Class ResourceHolderSynchronization<H extends ResourceHolder,K> 
- Type Parameters:
- H- the resource holder type
- K- the resource key type
- All Implemented Interfaces:
- Flushable,- Ordered,- TransactionSynchronization
TransactionSynchronization implementation that manages a
 ResourceHolder bound through TransactionSynchronizationManager.- Since:
- 2.5.5
- Author:
- Juergen Hoeller
- 
Field SummaryFields inherited from interface org.springframework.core.OrderedHIGHEST_PRECEDENCE, LOWEST_PRECEDENCEFields inherited from interface org.springframework.transaction.support.TransactionSynchronizationSTATUS_COMMITTED, STATUS_ROLLED_BACK, STATUS_UNKNOWN
- 
Constructor SummaryConstructorsConstructorDescriptionResourceHolderSynchronization(H resourceHolder, K resourceKey) Create a new ResourceHolderSynchronization for the given holder.
- 
Method SummaryModifier and TypeMethodDescriptionvoidInvoked after transaction commit.voidafterCompletion(int status) Invoked after transaction commit/rollback.voidbeforeCommit(boolean readOnly) Invoked before transaction commit (before "beforeCompletion").voidInvoked before transaction commit/rollback.protected voidcleanupResource(H resourceHolder, K resourceKey, boolean committed) Perform a cleanup on the given resource (which is left bound to the thread).voidflush()Flush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.protected voidflushResource(H resourceHolder) Flush callback for the given resource holder.protected voidprocessResourceAfterCommit(H resourceHolder) After-commit callback for the given resource holder.protected voidreleaseResource(H resourceHolder, K resourceKey) Release the given resource (after it has been unbound from the thread).voidresume()Resume this synchronization.protected booleanshouldReleaseAfterCompletion(H resourceHolder) Return whether this holder's resource should be released after transaction completion (true).protected booleanReturn whether this holder's resource should be released before transaction completion (true) or rather after transaction completion (false).protected booleanReturn whether this holder should be unbound at completion (or should rather be left bound to the thread after the transaction).voidsuspend()Suspend this synchronization.Methods inherited from class java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.springframework.transaction.support.TransactionSynchronizationgetOrder, savepoint, savepointRollback
- 
Constructor Details- 
ResourceHolderSynchronizationCreate a new ResourceHolderSynchronization for the given holder.- Parameters:
- resourceHolder- the ResourceHolder to manage
- resourceKey- the key to bind the ResourceHolder for
- See Also:
 
 
- 
- 
Method Details- 
suspendpublic void suspend()Description copied from interface:TransactionSynchronizationSuspend this synchronization. Supposed to unbind resources from TransactionSynchronizationManager if managing any.- Specified by:
- suspendin interface- TransactionSynchronization
- See Also:
 
- 
resumepublic void resume()Description copied from interface:TransactionSynchronizationResume this synchronization. Supposed to rebind resources to TransactionSynchronizationManager if managing any.- Specified by:
- resumein interface- TransactionSynchronization
- See Also:
 
- 
flushpublic void flush()Description copied from interface:TransactionSynchronizationFlush the underlying session to the datastore, if applicable: for example, a Hibernate/JPA session.- Specified by:
- flushin interface- Flushable
- Specified by:
- flushin interface- TransactionSynchronization
- See Also:
 
- 
beforeCommitpublic void beforeCommit(boolean readOnly) Description copied from interface:TransactionSynchronizationInvoked before transaction commit (before "beforeCompletion"). Can, for example, 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 interface- TransactionSynchronization
- Parameters:
- readOnly- whether the transaction is defined as read-only transaction
- See Also:
 
- 
beforeCompletionpublic 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.- Specified by:
- beforeCompletionin interface- TransactionSynchronization
- See Also:
 
- 
afterCommitpublic void afterCommit()Description copied from interface:TransactionSynchronizationInvoked after transaction commit. Can perform further operations right after the main transaction has successfully committed.Can, for example, 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 interface- TransactionSynchronization
 
- 
afterCompletionpublic void afterCompletion(int status) 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 interface- TransactionSynchronization
- Parameters:
- status- completion status according to the- STATUS_*constants
- See Also:
 
- 
shouldUnbindAtCompletionprotected boolean shouldUnbindAtCompletion()Return whether this holder should be unbound at completion (or should rather be left bound to the thread after the transaction).The default implementation returns true.
- 
shouldReleaseBeforeCompletionprotected boolean shouldReleaseBeforeCompletion()Return whether this holder's resource should be released before transaction completion (true) or rather after transaction completion (false).Note that resources will only be released when they are unbound from the thread ( shouldUnbindAtCompletion()).The default implementation returns true.- See Also:
 
- 
shouldReleaseAfterCompletionReturn whether this holder's resource should be released after transaction completion (true).The default implementation returns !shouldReleaseBeforeCompletion(), releasing after completion if no attempt was made before completion.- See Also:
 
- 
flushResourceFlush callback for the given resource holder.- Parameters:
- resourceHolder- the resource holder to flush
 
- 
processResourceAfterCommitAfter-commit callback for the given resource holder. Only called when the resource hasn't been released yet (shouldReleaseBeforeCompletion()).- Parameters:
- resourceHolder- the resource holder to process
 
- 
releaseResourceRelease the given resource (after it has been unbound from the thread).- Parameters:
- resourceHolder- the resource holder to process
- resourceKey- the key that the ResourceHolder was bound for
 
- 
cleanupResourcePerform a cleanup on the given resource (which is left bound to the thread).- Parameters:
- resourceHolder- the resource holder to process
- resourceKey- the key that the ResourceHolder was bound for
- committed- whether the transaction has committed (- true) or rolled back (- false)
 
 
-