Add no-op TransactionOperations implementation #23198
Closed
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.
A no-op implementation can be useful for:
TransactionOperations
consuming code switch to non-transactional behavior by injectingNoOpTransactionOperations
instead ofTransactionTemplate
For first point we have a use case in Spring Session's
JdbcOperationsSessionRepository
. I've used similar approach in a number of other projects so having Framework provide it OOTB would be nice. Also note thatTransactionOperations
isn't parameterized, butTransactionOperations#execute
is which makes it impossible to have no-op implementation as lambda expression.