| org.springframework.transaction.support.TransactionSynchronization
All known Subclasses: org.springframework.transaction.support.TransactionSynchronizationAdapter,
| Method Summary | |
| void | afterCommit()
Invoked after transaction commit. | | 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. | | void | beforeCommit(boolean readOnly)
Invoked before transaction commit (before "beforeCompletion").
Can e.g. | | void | beforeCompletion()
Invoked before transaction commit/rollback.
Can perform resource cleanup before transaction completion.
This method will be invoked after beforeCommit, even when
beforeCommit threw an exception. | | void | resume()
Resume this synchronization. | | void | suspend()
Suspend this synchronization. |
| STATUS_COMMITTED | | int STATUS_COMMITTED(Code) | | Completion status in case of proper commit
|
| STATUS_ROLLED_BACK | | int STATUS_ROLLED_BACK(Code) | | Completion status in case of proper rollback
|
| STATUS_UNKNOWN | | int STATUS_UNKNOWN(Code) | | Completion status in case of heuristic mixed completion or system errors
|
| afterCommit | | void afterCommit()(Code) | | 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.
throws:
RuntimeException - in case of errors; will be propagated to the caller(note: do not throw TransactionException subclasses here!) |
| afterCompletion | | void afterCompletion(int status)(Code) | | 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.
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: TransactionSynchronization.STATUS_COMMITTED
See Also: TransactionSynchronization.STATUS_ROLLED_BACK
See Also: TransactionSynchronization.STATUS_UNKNOWN
See Also: TransactionSynchronization.beforeCompletion |
| beforeCommit | | void beforeCommit(boolean readOnly)(Code) | | Invoked before transaction commit (before "beforeCompletion").
Can e.g. flush transactional O/R Mapping sessions to the database.
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: TransactionSynchronization.beforeCompletion |
| beforeCompletion | | void beforeCompletion()(Code) | | Invoked before transaction commit/rollback.
Can perform resource cleanup before transaction completion.
This method will be invoked after beforeCommit, even when
beforeCommit threw 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: TransactionSynchronization.beforeCommit
See Also: TransactionSynchronization.afterCompletion |
|
|