Interface TransactionSynchronization
- All Known Implementing Classes:
- ReactiveResourceSynchronization
AbstractReactiveTransactionManager.
 TransactionSynchronization implementations can implement the
 Ordered interface to influence their execution order.
 A synchronization that does not implement the Ordered
 interface is appended to the end of the synchronization chain.
 
System synchronizations performed by Spring itself use specific order values, allowing for fine-grained interaction with their execution order (if necessary).
- Since:
- 5.2
- Author:
- Mark Paluch, Juergen Hoeller
- See Also:
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final intCompletion status in case of proper commit.static final intCompletion status in case of proper rollback.static final intCompletion status in case of heuristic mixed completion or system errors.
- 
Method SummaryModifier and TypeMethodDescriptiondefault reactor.core.publisher.Mono<Void>Invoked after transaction commit.default reactor.core.publisher.Mono<Void>afterCompletion(int status) Invoked after transaction commit/rollback.default reactor.core.publisher.Mono<Void>beforeCommit(boolean readOnly) Invoked before transaction commit (before "beforeCompletion").default reactor.core.publisher.Mono<Void>Invoked before transaction commit/rollback.default reactor.core.publisher.Mono<Void>resume()Resume this synchronization.default reactor.core.publisher.Mono<Void>suspend()Suspend this synchronization.
- 
Field Details- 
STATUS_COMMITTEDstatic final int STATUS_COMMITTEDCompletion status in case of proper commit.- See Also:
 
- 
STATUS_ROLLED_BACKstatic final int STATUS_ROLLED_BACKCompletion status in case of proper rollback.- See Also:
 
- 
STATUS_UNKNOWNstatic final int STATUS_UNKNOWNCompletion status in case of heuristic mixed completion or system errors.- See Also:
 
 
- 
- 
Method Details- 
suspendSuspend this synchronization. Supposed to unbind resources from TransactionSynchronizationManager if managing any.
- 
resumeResume this synchronization. Supposed to rebind resources to TransactionSynchronizationManager if managing any.
- 
beforeCommitInvoked before transaction commit (before "beforeCompletion").This callback does not mean that the transaction will actually be committed. A rollback decision can still occur after this method has been called. This callback is rather meant to perform work that's only relevant if a commit still has a chance to happen, such as flushing SQL statements to the database. Note that exceptions will get propagated to the commit caller and cause a rollback of the transaction. - Parameters:
- readOnly- whether the transaction is defined as read-only transaction
- Throws:
- RuntimeException- in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)
- See Also:
 
- 
beforeCompletionInvoked before transaction commit/rollback. Can perform resource cleanup before transaction completion.This method will be invoked after beforeCommit, even whenbeforeCommitthrew an exception. This callback allows for closing resources before transaction completion, for any outcome.- Throws:
- RuntimeException- in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)
- See Also:
 
- 
afterCommitInvoked after transaction commit. Can perform further operations right after the main transaction has successfully committed.Can e.g. commit further operations that are supposed to follow on a successful commit of the main transaction, like confirmation messages or emails. NOTE: The transaction will have been committed already, but the transactional resources might still be active and accessible. As a consequence, any data access code triggered at this point will still "participate" in the original transaction, allowing to perform some cleanup (with no commit following anymore!), unless it explicitly declares that it needs to run in a separate transaction. Hence: Use PROPAGATION_REQUIRES_NEWfor any transactional operation that is called from here.- Throws:
- RuntimeException- in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)
 
- 
afterCompletionInvoked after transaction commit/rollback. Can perform resource cleanup after transaction completion.NOTE: The transaction will have been committed or rolled back already, but the transactional resources might still be active and accessible. As a consequence, any data access code triggered at this point will still "participate" in the original transaction, allowing to perform some cleanup (with no commit following anymore!), unless it explicitly declares that it needs to run in a separate transaction. Hence: Use PROPAGATION_REQUIRES_NEWfor any transactional operation that is called from here.- Parameters:
- status- completion status according to the- STATUS_*constants
- Throws:
- RuntimeException- in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)
- See Also:
 
 
-