Class SessionSynchronization
- java.lang.Object
-
- io.micronaut.transaction.hibernate5.SessionSynchronization
-
- All Implemented Interfaces:
io.micronaut.core.order.Ordered
,TransactionSynchronization
,java.io.Flushable
@Internal public class SessionSynchronization extends java.lang.Object implements TransactionSynchronization, io.micronaut.core.order.Ordered
Callback for resource cleanup at the end of a Spring-managed transaction for a pre-bound Hibernate Session.- Since:
- 4.2
- Author:
- Juergen Hoeller, graemerocher
-
-
Nested Class Summary
-
Nested classes/interfaces inherited from interface io.micronaut.transaction.support.TransactionSynchronization
TransactionSynchronization.Status
-
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description void
afterCommit()
Invoked after transaction commit.void
afterCompletion(TransactionSynchronization.Status 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.int
getOrder()
void
resume()
Resume this synchronization.void
suspend()
Suspend this synchronization.
-
-
-
Method Detail
-
getOrder
public int getOrder()
- Specified by:
getOrder
in interfaceio.micronaut.core.order.Ordered
-
suspend
public void suspend()
Description copied from interface:TransactionSynchronization
Suspend this synchronization. Supposed to unbind resources from TransactionSynchronizationManager if managing any.- Specified by:
suspend
in interfaceTransactionSynchronization
- See Also:
TransactionSynchronizationManager.unbindResource(java.lang.Object)
-
resume
public void resume()
Description copied from interface:TransactionSynchronization
Resume this synchronization. Supposed to rebind resources to TransactionSynchronizationManager if managing any.- Specified by:
resume
in interfaceTransactionSynchronization
- See Also:
TransactionSynchronizationManager.bindResource(java.lang.Object, java.lang.Object)
-
flush
public void flush()
Description copied from interface:TransactionSynchronization
Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.- Specified by:
flush
in interfacejava.io.Flushable
- Specified by:
flush
in interfaceTransactionSynchronization
- See Also:
TransactionStatus.flush()
-
beforeCommit
public void beforeCommit(boolean readOnly) throws TransactionException
Description copied from interface:TransactionSynchronization
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.
- Specified by:
beforeCommit
in interfaceTransactionSynchronization
- Parameters:
readOnly
- whether the transaction is defined as read-only transaction- Throws:
TransactionException
- See Also:
TransactionSynchronization.beforeCompletion()
-
beforeCompletion
public void beforeCompletion()
Description copied from interface:TransactionSynchronization
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.
-
afterCommit
public void afterCommit()
Description copied from interface:TransactionSynchronization
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.- Specified by:
afterCommit
in interfaceTransactionSynchronization
-
afterCompletion
public void afterCompletion(@NonNull TransactionSynchronization.Status status)
Description copied from interface:TransactionSynchronization
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.- Specified by:
afterCompletion
in interfaceTransactionSynchronization
- Parameters:
status
- completion status according to theSTATUS_*
constants- See Also:
TransactionSynchronization.Status.COMMITTED
,TransactionSynchronization.Status.ROLLED_BACK
,TransactionSynchronization.Status.UNKNOWN
,TransactionSynchronization.beforeCompletion()
-
-