SPR-16162 make JpaVendorAdapter configuration properties more transaction type aware #1591
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
As discussed on JIRA, a slightly different revision with the same intent is now in master. I'll backport it to 4.3.x over the weekend; it'd be great if you give it a try before the 5.0.2 / 4.3.13 release (mid next week). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Autoconfigure based on the transaction type if detected. If the transaction type cannot be detected for whatever reason, it falls back to the current behavior.
This is basically to prevent the Vendor Adapter to set an invalid connection release mode for JTA transactions but can be used for further configuration based on the detected transaction type.
Running the application with embedded tomcat:
Running with weblogic
