|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface TransactionSynchronization
Interface for transaction synchronization callbacks. Supported by AbstractPlatformTransactionManager.
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).
TransactionSynchronizationManager
,
AbstractPlatformTransactionManager
,
DataSourceUtils.CONNECTION_SYNCHRONIZATION_ORDER
,
SessionFactoryUtils.SESSION_SYNCHRONIZATION_ORDER
Field Summary | |
---|---|
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 |
Method Summary | |
---|---|
void |
afterCommit()
Invoked after transaction commit. |
void |
afterCompletion(int status)
Invoked after transaction commit/rollback. |
void |
beforeCommit(boolean readOnly)
Invoked before transaction commit (before "beforeCompletion"). |
void |
beforeCompletion()
Invoked before transaction commit/rollback. |
void |
flush()
Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session. |
void |
resume()
Resume this synchronization. |
void |
suspend()
Suspend this synchronization. |
Field Detail |
---|
static final int STATUS_COMMITTED
static final int STATUS_ROLLED_BACK
static final int STATUS_UNKNOWN
Method Detail |
---|
void suspend()
TransactionSynchronizationManager.unbindResource(java.lang.Object)
void resume()
TransactionSynchronizationManager.bindResource(java.lang.Object, java.lang.Object)
void flush()
TransactionStatus.flush()
void beforeCommit(boolean readOnly)
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()
void beforeCompletion()
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.
RuntimeException
- in case of errors; will be logged but not propagated
(note: do not throw TransactionException subclasses here!)beforeCommit(boolean)
,
afterCompletion(int)
void afterCommit()
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!)void afterCompletion(int status)
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 the STATUS_*
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()
|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |