public abstract class TransactionSynchronizationAdapter extends java.lang.Object implements TransactionSynchronization, Ordered
TransactionSynchronizationadapter containing empty method implementations, for easier overriding of single methods.
Also implements the
Ordered interface to enable the execution
order of synchronizations to be controlled declaratively. The default
late execution; return a lower value for earlier execution.
STATUS_COMMITTED, STATUS_ROLLED_BACK, STATUS_UNKNOWN
|Constructor and Description|
|Modifier and Type||Method and Description|
Invoked after transaction commit.
Invoked after transaction commit/rollback.
Invoked before transaction commit (before "beforeCompletion").
Invoked before transaction commit/rollback.
Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.
Get the order value of this object.
Resume this synchronization.
Suspend this synchronization.
public int getOrder()
Higher values are interpreted as lower priority. As a consequence,
the object with the lowest value has the highest priority (somewhat
analogous to Servlet
Same order values will result in arbitrary sort positions for the affected objects.
public void suspend()
public void resume()
public void flush()
public 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.
public 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.
public 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.
public 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
for any transactional operation that is called from here.
status- completion status according to the