spring-projects / spring-projects/spring-modulith
spring-modulith-events-jpa: Option to configure which TransactionManager that the JPA repository/registry should use
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
In scenarios with multiple datasources and transaction managers it would be nice to be able to set a specific TransactionManager instance and not rely on the default, in cases where other components also relies on the default one but expects it to be from a different datasource.
Something akin to what you might do with your own repos:
@EnableJpaRepositories(
entityManagerFactoryRef = "forModulith",
transactionManagerRef = "txmForModulith"
)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the spring-modulith-events-jpa module and the @EnableJpaRepositories configuration pattern, but no repository files or tests. Start by locating that module’s JPA repository and registry setup and how its transaction manager is selected. Done means callers can configure a specific transaction manager without changing the default used by other components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100