-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Overriding transaction management [BATCH-2294] #1289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Michael Minella commented Can you please provide your configuration? |
Thiago B. Negri commented I'm facing the same issue. As a workaround I've defined the exact same transaction manager I already have defined in other configuration class in my Spring Batch configuration class. So my application starts defining my transaction manager, then gets overridden by Spring Batch transaction manager and then gets overridden by my second definition of the transaction manager. Sweet. Adding a |
Martin Meyer commented I'm not sure what this magic
Basically I just try to autowire a transaction manager and make a new one only if there isn't one. |
Mahmoud Ben Hassine commented This issue is resolved with #634. In order to provide a custom transaction manager, a custom
Documentation was updated accordingly (See https://github.com/spring-projects/spring-batch/pull/620/files). |
Abhay opened BATCH-2294 and commented
SimpleBatchConfiguration which gets loaded by any of spring application, created transactionManager bean irrespective of whether that bean is already created or not. This results in overriding transaction manager
@ConditionalOnMissingBean
could be used for resolution of this issuesAffects: 3.0.1
Reference URL: http://stackoverflow.com/q/25303163/3073323
Issue Links:
("is depended on by")
Referenced from: pull request #609, and commits a68d700
Backported to: 4.1.0.M3
3 votes, 5 watchers
The text was updated successfully, but these errors were encountered: