Class SessionSynchronization
- All Implemented Interfaces:
io.micronaut.core.order.Ordered,TransactionSynchronization,Flushable
- Since:
- 4.2
- Author:
- Juergen Hoeller, graemerocher
-
Nested Class Summary
Nested classes/interfaces inherited from interface io.micronaut.transaction.support.TransactionSynchronization
TransactionSynchronization.Status -
Field Summary
Fields inherited from interface io.micronaut.core.order.Ordered
HIGHEST_PRECEDENCE, LOWEST_PRECEDENCE -
Method Summary
Modifier and TypeMethodDescriptionvoidInvoked after transaction commit.voidInvoked after transaction commit/rollback.voidbeforeCommit(boolean readOnly) Invoked before transaction commit (before "beforeCompletion").voidInvoked before transaction commit/rollback.voidflush()Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.intgetOrder()voidresume()Resume this synchronization.voidsuspend()Suspend this synchronization.
-
Method Details
-
getOrder
public int getOrder()- Specified by:
getOrderin interfaceio.micronaut.core.order.Ordered
-
suspend
public void suspend()Description copied from interface:TransactionSynchronizationSuspend this synchronization. Supposed to unbind resources from TransactionSynchronizationManager if managing any.- Specified by:
suspendin interfaceTransactionSynchronization- See Also:
-
resume
public void resume()Description copied from interface:TransactionSynchronizationResume this synchronization. Supposed to rebind resources to TransactionSynchronizationManager if managing any.- Specified by:
resumein interfaceTransactionSynchronization- See Also:
-
flush
public void flush()Description copied from interface:TransactionSynchronizationFlush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.- Specified by:
flushin interfaceFlushable- Specified by:
flushin interfaceTransactionSynchronization- See Also:
-
TransactionStatus.flush()
-
beforeCommit
Description copied from interface:TransactionSynchronizationInvoked 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.
- Specified by:
beforeCommitin interfaceTransactionSynchronization- Parameters:
readOnly- whether the transaction is defined as read-only transaction- Throws:
TransactionException- See Also:
-
beforeCompletion
public void beforeCompletion()Description copied from interface:TransactionSynchronizationInvoked 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. -
afterCommit
public void afterCommit()Description copied from interface:TransactionSynchronizationInvoked 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.- Specified by:
afterCommitin interfaceTransactionSynchronization
-
afterCompletion
Description copied from interface:TransactionSynchronizationInvoked 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.- Specified by:
afterCompletionin interfaceTransactionSynchronization- Parameters:
status- completion status according to theSTATUS_*constants- See Also:
-