接口 TransactionSynchronization
- 所有已知实现类:
ReactiveResourceSynchronization
public interface TransactionSynchronization
Interface for reactive transaction synchronization callbacks. Supported byAbstractReactiveTransactionManager
.TransactionSynchronization implementations can implement the
Ordered
interface to influence their execution order. A synchronization that does not implement theOrdered
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).
- 从以下版本开始:
- 5.2
- 作者:
- Mark Paluch, Juergen Hoeller
- 另请参阅:
TransactionSynchronizationManager
,AbstractReactiveTransactionManager
字段概要
字段 修饰符和类型 字段 说明 static int
STATUS_COMMITTED
Completion status in case of proper commit.static int
STATUS_ROLLED_BACK
Completion status in case of proper rollback.static int
STATUS_UNKNOWN
Completion status in case of heuristic mixed completion or system errors.
方法概要
所有方法 实例方法 默认方法 修饰符和类型 方法 说明 default reactor.core.publisher.Mono<Void>
afterCommit()
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>
beforeCompletion()
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.
字段详细资料
STATUS_COMMITTED
static final int STATUS_COMMITTED
Completion status in case of proper commit.- 另请参阅:
- 常量字段值
STATUS_ROLLED_BACK
static final int STATUS_ROLLED_BACK
Completion status in case of proper rollback.- 另请参阅:
- 常量字段值
STATUS_UNKNOWN
static final int STATUS_UNKNOWN
Completion status in case of heuristic mixed completion or system errors.- 另请参阅:
- 常量字段值
方法详细资料
suspend
default reactor.core.publisher.Mono<Void> suspend()
Suspend this synchronization. Supposed to unbind resources from TransactionSynchronizationManager if managing any.
resume
default reactor.core.publisher.Mono<Void> resume()
Resume this synchronization. Supposed to rebind resources to TransactionSynchronizationManager if managing any.
beforeCommit
default reactor.core.publisher.Mono<Void> beforeCommit(boolean readOnly)
Invoked 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.
- 参数:
readOnly
- whether the transaction is defined as read-only transaction- 抛出:
RuntimeException
- in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)- 另请参阅:
beforeCompletion()
beforeCompletion
default reactor.core.publisher.Mono<Void> beforeCompletion()
Invoked before transaction commit/rollback. Can perform resource cleanup before transaction completion.This method will be invoked after
beforeCommit
, even whenbeforeCommit
threw an exception. This callback allows for closing resources before transaction completion, for any outcome.- 抛出:
RuntimeException
- in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)- 另请参阅:
beforeCommit(boolean)
,afterCompletion(int)
afterCommit
default reactor.core.publisher.Mono<Void> afterCommit()
Invoked 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_NEW
for any transactional operation that is called from here.- 抛出:
RuntimeException
- in case of errors; will be propagated to the caller (note: do not throw TransactionException subclasses here!)
afterCompletion
default reactor.core.publisher.Mono<Void> afterCompletion(int status)
Invoked 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_NEW
for any transactional operation that is called from here.- 参数:
status
- completion status according to theSTATUS_*
constants- 抛出:
RuntimeException
- in case of errors; will be logged but not propagated (note: do not throw TransactionException subclasses here!)- 另请参阅:
STATUS_COMMITTED
,STATUS_ROLLED_BACK
,STATUS_UNKNOWN
,beforeCompletion()