org.springframework.transaction.support

Class SimpleTransactionScope.CleanupSynchronization

java.lang.Object

org.springframework.transaction.support.TransactionSynchronizationAdapter

org.springframework.transaction.support.SimpleTransactionScope.CleanupSynchronization

All Implemented Interfaces:

java.io.Flushable, Ordered, TransactionSynchronization

Enclosing class:

SimpleTransactionScope

private class SimpleTransactionScope.CleanupSynchronization
extends TransactionSynchronizationAdapter

Field Summary

Fields inherited from interface org.springframework.transaction.support.TransactionSynchronization

STATUS_COMMITTED, STATUS_ROLLED_BACK, STATUS_UNKNOWN

Fields inherited from interface org.springframework.core.Ordered

HIGHEST_PRECEDENCE, LOWEST_PRECEDENCE

Constructor Summary

Constructors

Modifier	Constructor and Description
private	CleanupSynchronization()

Method Summary

Modifier and Type	Method and Description
void	afterCompletion(int status) Invoked after transaction commit/rollback.

Methods inherited from class org.springframework.transaction.support.TransactionSynchronizationAdapter

afterCommit, beforeCommit, beforeCompletion, flush, getOrder, resume, suspend

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CleanupSynchronization

private CleanupSynchronization()

Method Detail

afterCompletion

public void afterCompletion(int 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 interface TransactionSynchronization

Overrides:

afterCompletion in class TransactionSynchronizationAdapter

Parameters:

status - completion status according to the STATUS_* constants

See Also:

TransactionSynchronization.STATUS_COMMITTED, TransactionSynchronization.STATUS_ROLLED_BACK, TransactionSynchronization.STATUS_UNKNOWN, TransactionSynchronization.beforeCompletion()