|
The Spring Framework | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object org.springframework.transaction.support.AbstractPlatformTransactionManager org.springframework.transaction.jta.JtaTransactionManager
public class JtaTransactionManager
PlatformTransactionManager
implementation
for JTA, delegating to a backend JTA provider. This is typically used to delegate
to a J2EE server's transaction coordinator, but may also be configured with a
local JTA provider which is embedded within the application.
This transaction manager is appropriate for handling distributed transactions, i.e. transactions that span multiple resources, and for controlling transactions on application server resources (e.g. JDBC DataSources available in JNDI) in general. For a single JDBC DataSource, DataSourceTransactionManager is perfectly sufficient, and for accessing a single resource with Hibernate (including transactional cache), HibernateTransactionManager is appropriate, for example.
Transaction synchronization is active by default, to allow data access support classes to register resources that are opened within the transaction for closing at transaction completion time. Spring's support classes for JDBC, Hibernate, JDO etc all perform such registration, allowing for reuse of the same Hibernate Session etc within the transaction. Standard JTA does not even guarantee that for Connections from a transactional JDBC DataSource: Spring's synchronization solves those issues.
For typical JTA transactions (REQUIRED, SUPPORTS, MANDATORY, NEVER), a plain JtaTransactionManager definition is all you need, completely portable across all J2EE servers. This corresponds to the functionality of the JTA UserTransaction, for which J2EE specifies a standard JNDI name ("java:comp/UserTransaction"). There is no need to configure a server-specific TransactionManager lookup for this kind of JTA usage.
Note: Advanced JTA usage below. Dealing with these mechanisms is not necessary for typical usage scenarios.
Transaction suspension (REQUIRES_NEW, NOT_SUPPORTED) is just available with a JTA TransactionManager being registered, via the "transactionManagerName" or "transactionManager" property. The location of this well-defined JTA object is not specified by J2EE; it is specific to each J2EE server, often kept in JNDI like the JTA UserTransaction. Some well-known JNDI locations are:
All of these cases are autodetected by JtaTransactionManager (since Spring 1.2), provided that the "autodetectTransactionManager" flag is set to "true" (which it is by default). Consequently, JtaTransactionManager will support transaction suspension out-of-the-box on many J2EE servers.
A JNDI lookup can also be factored out into a corresponding
JndiObjectFactoryBean
, passed into
JtaTransactionManager's "transactionManager" property. Such a bean definition
can then be reused by other objects, for example Spring's LocalSessionFactoryBean
for Hibernate.
For IBM WebSphere and standalone JOTM, static accessor methods are required to
obtain the JTA TransactionManager: Therefore, WebSphere and JOTM have their own
FactoryBean implementations, to be wired with the "transactionManager" property.
In case of JotmFactoryBean
, the same JTA object implements UserTransaction
too: Therefore, passing the object to the "userTransaction" property is sufficient.
It is also possible to specify a JTA TransactionManager only, either through
the corresponding constructor or through the "transactionManager" property.
In the latter case, the "userTransactionName" property needs to be set to null
,
to suppress the default "java:comp/UserTransaction" JNDI lookup and thus enforce
use of the given JTA TransactionManager even for begin, commit and rollback.
Note: Support for the JTA TransactionManager interface is not required by J2EE.
Almost all J2EE servers expose it, but do so as extension to J2EE. There might be some
issues with compatibility, despite the TransactionManager interface being part of JTA.
The only currently known problem is resuming a transaction on WebLogic, which by default
fails if the suspended transaction was marked rollback-only; for other usages, it works
properly. Use Spring's WebLogicJtaTransactionManager
to address this issue.
This standard JtaTransactionManager supports timeouts but not per-transaction
isolation levels. Custom subclasses may override doJtaBegin(org.springframework.transaction.jta.JtaTransactionObject, org.springframework.transaction.TransactionDefinition)
for
specific JTA extensions in order to provide this functionality; Spring includes
corresponding WebLogicJtaTransactionManager
and OC4JJtaTransactionManager
classes, for BEA's WebLogic Server and Oracle's OC4J, respectively. Such adapters
for specific J2EE transaction coordinators may also expose transaction names for
monitoring (both of the above do); with standard JTA, transaction names will simply
be ignored.
This class is serializable. However, active synchronizations do not survive serialization.
setUserTransactionName(java.lang.String)
,
setUserTransaction(javax.transaction.UserTransaction)
,
setTransactionManagerName(java.lang.String)
,
setTransactionManager(javax.transaction.TransactionManager)
,
doJtaBegin(org.springframework.transaction.jta.JtaTransactionObject, org.springframework.transaction.TransactionDefinition)
,
JotmFactoryBean
,
WebSphereTransactionManagerFactoryBean
,
WebLogicJtaTransactionManager
,
JndiObjectFactoryBean
,
LocalSessionFactoryBean.setJtaTransactionManager(javax.transaction.TransactionManager)
,
Serialized FormNested Class Summary |
---|
Nested classes/interfaces inherited from class org.springframework.transaction.support.AbstractPlatformTransactionManager |
---|
AbstractPlatformTransactionManager.SuspendedResourcesHolder |
Field Summary | |
---|---|
static String |
DEFAULT_USER_TRANSACTION_NAME
Default JNDI location for the JTA UserTransaction. |
static String[] |
FALLBACK_TRANSACTION_MANAGER_NAMES
Fallback JNDI locations for the JTA TransactionManager. |
Fields inherited from class org.springframework.transaction.support.AbstractPlatformTransactionManager |
---|
logger, SYNCHRONIZATION_ALWAYS, SYNCHRONIZATION_NEVER, SYNCHRONIZATION_ON_ACTUAL_TRANSACTION |
Constructor Summary | |
---|---|
JtaTransactionManager()
Create a new JtaTransactionManager instance, to be configured as bean. |
|
JtaTransactionManager(TransactionManager transactionManager)
Create a new JtaTransactionManager instance. |
|
JtaTransactionManager(UserTransaction userTransaction)
Create a new JtaTransactionManager instance. |
|
JtaTransactionManager(UserTransaction userTransaction,
TransactionManager transactionManager)
Create a new JtaTransactionManager instance. |
Method Summary | |
---|---|
void |
afterPropertiesSet()
Initialize the UserTransaction as well as the TransactionManager handle. |
protected void |
applyIsolationLevel(JtaTransactionObject txObject,
int isolationLevel)
Apply the given transaction isolation level. |
protected void |
applyTimeout(JtaTransactionObject txObject,
int timeout)
Apply the given transaction timeout. |
protected UserTransaction |
buildUserTransaction(TransactionManager transactionManager)
Build a UserTransaction handle based on the given TransactionManager. |
protected void |
doBegin(Object transaction,
TransactionDefinition definition)
Begin a new transaction with semantics according to the given transaction definition. |
protected void |
doCommit(DefaultTransactionStatus status)
Perform an actual commit of the given transaction. |
protected JtaTransactionObject |
doGetJtaTransaction(UserTransaction ut)
Get a JTA transaction object for the given current UserTransaction. |
protected Object |
doGetTransaction()
This implementation returns a JtaTransactionObject instance for the JTA UserTransaction. |
protected void |
doJtaBegin(JtaTransactionObject txObject,
TransactionDefinition definition)
Perform a JTA begin on the JTA UserTransaction or TransactionManager. |
protected void |
doJtaResume(JtaTransactionObject txObject,
Object suspendedTransaction)
Perform a JTA resume on the JTA TransactionManager. |
protected Object |
doJtaSuspend(JtaTransactionObject txObject)
Perform a JTA suspend on the JTA TransactionManager. |
protected void |
doRegisterAfterCompletionWithJtaTransaction(JtaTransactionObject txObject,
List synchronizations)
Register a JTA synchronization on the JTA TransactionManager, for calling afterCompletion on the given Spring TransactionSynchronizations. |
protected void |
doResume(Object transaction,
Object suspendedResources)
Resume the resources of the current transaction. |
protected void |
doRollback(DefaultTransactionStatus status)
Perform an actual rollback of the given transaction. |
protected void |
doSetRollbackOnly(DefaultTransactionStatus status)
Set the given transaction rollback-only. |
protected Object |
doSuspend(Object transaction)
Suspend the resources of the current transaction. |
protected TransactionManager |
findTransactionManager(UserTransaction ut)
Find the JTA TransactionManager through autodetection: checking whether the UserTransaction object implements the TransactionManager, and checking the fallback JNDI locations. |
protected UserTransaction |
findUserTransaction()
Find the JTA UserTransaction through a default JNDI lookup: "java:comp/UserTransaction". |
Properties |
getJndiEnvironment()
Return the JNDI environment to use for JNDI lookups. |
JndiTemplate |
getJndiTemplate()
Return the JndiTemplate used for JNDI lookups. |
TransactionManager |
getTransactionManager()
Return the JTA TransactionManager that this transaction manager uses. |
UserTransaction |
getUserTransaction()
Return the JTA UserTransaction that this transaction manager uses. |
protected void |
initUserTransactionAndTransactionManager()
Initialize the UserTransaction as well as the TransactionManager handle. |
protected boolean |
isExistingTransaction(Object transaction)
Check if the given transaction object indicates an existing transaction (that is, a transaction which has already started). |
protected TransactionManager |
lookupTransactionManager(String transactionManagerName)
Look up the JTA TransactionManager in JNDI via the configured name. |
protected UserTransaction |
lookupUserTransaction(String userTransactionName)
Look up the JTA UserTransaction in JNDI via the configured name. |
protected void |
registerAfterCompletionWithExistingTransaction(Object transaction,
List synchronizations)
Register the given list of transaction synchronizations with the existing transaction. |
protected TransactionManager |
retrieveTransactionManager()
Allows subclasses to retrieve the JTA TransactionManager in a vendor-specific manner. |
protected UserTransaction |
retrieveUserTransaction()
Allows subclasses to retrieve the JTA UserTransaction in a vendor-specific manner. |
void |
setAllowCustomIsolationLevels(boolean allowCustomIsolationLevels)
Set whether to allow custom isolation levels to be specified. |
void |
setAutodetectTransactionManager(boolean autodetectTransactionManager)
Set whether to autodetect a JTA UserTransaction object that implements the JTA TransactionManager interface too (i.e. the JNDI location for the TransactionManager is "java:comp/UserTransaction", same as for the UserTransaction). |
void |
setAutodetectUserTransaction(boolean autodetectUserTransaction)
Set whether to autodetect the JTA UserTransaction at its default JNDI location "java:comp/UserTransaction", as specified by J2EE. |
void |
setCacheUserTransaction(boolean cacheUserTransaction)
Set whether to cache the JTA UserTransaction object fetched from JNDI. |
void |
setJndiEnvironment(Properties jndiEnvironment)
Set the JNDI environment to use for JNDI lookups. |
void |
setJndiTemplate(JndiTemplate jndiTemplate)
Set the JndiTemplate to use for JNDI lookups. |
void |
setTransactionManager(TransactionManager transactionManager)
Set the JTA TransactionManager to use as direct reference. |
void |
setTransactionManagerName(String transactionManagerName)
Set the JNDI name of the JTA TransactionManager. |
void |
setUserTransaction(UserTransaction userTransaction)
Set the JTA UserTransaction to use as direct reference. |
void |
setUserTransactionName(String userTransactionName)
Set the JNDI name of the JTA UserTransaction. |
protected boolean |
shouldCommitOnGlobalRollbackOnly()
This implementation returns "true": a JTA commit will properly handle transactions that have been marked rollback-only at a global level. |
protected boolean |
useSavepointForNestedTransaction()
This implementation returns false to cause a further invocation of doBegin despite an already existing transaction. |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Field Detail |
---|
public static final String DEFAULT_USER_TRANSACTION_NAME
public static final String[] FALLBACK_TRANSACTION_MANAGER_NAMES
Constructor Detail |
---|
public JtaTransactionManager()
afterPropertiesSet
to activate the configuration.
public JtaTransactionManager(UserTransaction userTransaction)
userTransaction
- the JTA UserTransaction to use as direct referencepublic JtaTransactionManager(UserTransaction userTransaction, TransactionManager transactionManager)
userTransaction
- the JTA UserTransaction to use as direct referencetransactionManager
- the JTA TransactionManager to use as direct referencepublic JtaTransactionManager(TransactionManager transactionManager)
transactionManager
- the JTA TransactionManager to use as direct referenceMethod Detail |
---|
public void setJndiTemplate(JndiTemplate jndiTemplate)
public JndiTemplate getJndiTemplate()
public void setJndiEnvironment(Properties jndiEnvironment)
public Properties getJndiEnvironment()
public void setUserTransaction(UserTransaction userTransaction)
Typically just used for local JTA setups; in a J2EE environment, the UserTransaction will always be fetched from JNDI.
public UserTransaction getUserTransaction()
public void setUserTransactionName(String userTransactionName)
Note that the UserTransaction will be autodetected at the J2EE default location "java:comp/UserTransaction" if not specified explicitly.
public void setAutodetectUserTransaction(boolean autodetectUserTransaction)
Default is "true", autodetecting the UserTransaction unless it has been specified explicitly. Turn this flag off to allow for JtaTransactionManager operating against the TransactionManager only, despite a default UserTransaction being available.
DEFAULT_USER_TRANSACTION_NAME
public void setCacheUserTransaction(boolean cacheUserTransaction)
Default is "true": UserTransaction lookup will only happen at startup, reusing the same UserTransaction handle for all transactions of all threads. This is the most efficient choice for all application servers that provide a shared UserTransaction object (the typical case).
Turn this flag off to enforce a fresh lookup of the UserTransaction for every transaction. This is only necessary for application servers that return a new UserTransaction for every transaction, keeping state tied to the UserTransaction object itself rather than the current thread.
public void setTransactionManager(TransactionManager transactionManager)
A TransactionManager is necessary for suspending and resuming transactions, as this not supported by the UserTransaction interface.
Note that the TransactionManager will be autodetected if the JTA UserTransaction object implements the JTA TransactionManager interface too, as well as autodetected at various well-known fallback JNDI locations.
public TransactionManager getTransactionManager()
public void setTransactionManagerName(String transactionManagerName)
A TransactionManager is necessary for suspending and resuming transactions, as this not supported by the UserTransaction interface.
Note that the TransactionManager will be autodetected if the JTA UserTransaction object implements the JTA TransactionManager interface too, as well as autodetected at various well-known fallback JNDI locations.
public void setAutodetectTransactionManager(boolean autodetectTransactionManager)
Default is "true", autodetecting the TransactionManager unless it has been specified explicitly. Can be turned off to deliberately ignore an available TransactionManager, for example when there are known issues with suspend/resume and any attempt to use REQUIRES_NEW or NOT_SUPPORTED should fail fast.
FALLBACK_TRANSACTION_MANAGER_NAMES
public void setAllowCustomIsolationLevels(boolean allowCustomIsolationLevels)
Default is "false", throwing an exception if a non-default isolation level is specified for a transaction. Turn this flag on if affected resource adapters check the thread-bound transaction context and apply the specified isolation levels individually (e.g. through a IsolationLevelDataSourceRouter).
IsolationLevelDataSourceRouter
public void afterPropertiesSet() throws TransactionSystemException
afterPropertiesSet
in interface InitializingBean
TransactionSystemException
initUserTransactionAndTransactionManager()
protected void initUserTransactionAndTransactionManager() throws TransactionSystemException
TransactionSystemException
- if initialization failedprotected UserTransaction lookupUserTransaction(String userTransactionName) throws TransactionSystemException
afterPropertiesSet
if no direct UserTransaction reference was set.
Can be overridden in subclasses to provide a different UserTransaction object.
userTransactionName
- the JNDI name of the UserTransaction
TransactionSystemException
- if the JNDI lookup failedsetJndiTemplate(org.springframework.jndi.JndiTemplate)
,
setUserTransactionName(java.lang.String)
protected TransactionManager lookupTransactionManager(String transactionManagerName) throws TransactionSystemException
afterPropertiesSet
if no direct TransactionManager reference was set.
Can be overridden in subclasses to provide a different TransactionManager object.
transactionManagerName
- the JNDI name of the TransactionManager
TransactionSystemException
- if the JNDI lookup failedsetJndiTemplate(org.springframework.jndi.JndiTemplate)
,
setTransactionManagerName(java.lang.String)
protected UserTransaction retrieveUserTransaction() throws TransactionSystemException
The default implementation simply returns null
.
null
if none found
TransactionSystemException
- in case of errorssetUserTransaction(javax.transaction.UserTransaction)
,
setUserTransactionName(java.lang.String)
protected TransactionManager retrieveTransactionManager() throws TransactionSystemException
The default implementation simply returns null
.
null
if none found
TransactionSystemException
- in case of errorssetTransactionManager(javax.transaction.TransactionManager)
,
setTransactionManagerName(java.lang.String)
protected UserTransaction findUserTransaction()
null
if not foundDEFAULT_USER_TRANSACTION_NAME
protected TransactionManager findTransactionManager(UserTransaction ut)
ut
- the JTA UserTransaction object
null
if not foundFALLBACK_TRANSACTION_MANAGER_NAMES
protected UserTransaction buildUserTransaction(TransactionManager transactionManager)
transactionManager
- the TransactionManager
protected Object doGetTransaction()
The UserTransaction object will either be looked up freshly for the current transaction, or the cached one looked up at startup will be used. The latter is the default: Most application servers use a shared singleton UserTransaction that can be cached. Turn off the "cacheUserTransaction" flag to enforce a fresh lookup for every transaction.
doGetTransaction
in class AbstractPlatformTransactionManager
setCacheUserTransaction(boolean)
protected JtaTransactionObject doGetJtaTransaction(UserTransaction ut)
Subclasses can override this to provide a JtaTransactionObject subclass, for example holding some additional JTA handle needed.
ut
- the UserTransaction handle to use for the current transaction
protected boolean isExistingTransaction(Object transaction)
AbstractPlatformTransactionManager
The result will be evaluated according to the specified propagation behavior for the new transaction. An existing transaction might get suspended (in case of PROPAGATION_REQUIRES_NEW), or the new transaction might participate in the existing one (in case of PROPAGATION_REQUIRED).
The default implementation returns false
, assuming that
participating in existing transactions is generally not supported.
Subclasses are of course encouraged to provide such support.
isExistingTransaction
in class AbstractPlatformTransactionManager
transaction
- transaction object returned by doGetTransaction
AbstractPlatformTransactionManager.doGetTransaction()
protected boolean useSavepointForNestedTransaction()
JTA implementations might support nested transactions via further
UserTransaction.begin()
invocations, but never support savepoints.
useSavepointForNestedTransaction
in class AbstractPlatformTransactionManager
protected void doBegin(Object transaction, TransactionDefinition definition)
AbstractPlatformTransactionManager
This method gets called when the transaction manager has decided to actually start a new transaction. Either there wasn't any transaction before, or the previous transaction has been suspended.
A special scenario is a nested transaction without savepoint: If
useSavepointForNestedTransaction()
returns "false", this method
will be called to start a nested transaction when necessary. In such a context,
there will be an active transaction: The implementation of this method has
to detect this and start an appropriate nested transaction.
doBegin
in class AbstractPlatformTransactionManager
transaction
- transaction object returned by doGetTransaction
definition
- TransactionDefinition instance, describing propagation
behavior, isolation level, read-only flag, timeout, and transaction nameprotected void doJtaBegin(JtaTransactionObject txObject, TransactionDefinition definition) throws NotSupportedException, SystemException
This implementation only supports standard JTA functionality: that is, no per-transaction isolation levels and no transaction names. Can be overridden in subclasses, for specific JTA implementations.
Calls applyIsolationLevel
and applyTimeout
before invoking the UserTransaction's begin
method.
txObject
- the JtaTransactionObject containing the UserTransactiondefinition
- TransactionDefinition instance, describing propagation
behavior, isolation level, read-only flag, timeout, and transaction name
NotSupportedException
- if thrown by JTA methods
SystemException
- if thrown by JTA methodsgetUserTransaction()
,
getTransactionManager()
,
applyIsolationLevel(org.springframework.transaction.jta.JtaTransactionObject, int)
,
applyTimeout(org.springframework.transaction.jta.JtaTransactionObject, int)
,
JtaTransactionObject.getUserTransaction()
,
UserTransaction.setTransactionTimeout(int)
,
UserTransaction.begin()
protected void applyIsolationLevel(JtaTransactionObject txObject, int isolationLevel) throws InvalidIsolationLevelException, SystemException
To be overridden in subclasses for specific JTA implementations,
as alternative to overriding the full doJtaBegin(org.springframework.transaction.jta.JtaTransactionObject, org.springframework.transaction.TransactionDefinition)
method.
txObject
- the JtaTransactionObject containing the UserTransactionisolationLevel
- isolation level taken from transaction definition
InvalidIsolationLevelException
- if the given isolation level
cannot be applied
SystemException
- if thrown by the JTA implementationdoJtaBegin(org.springframework.transaction.jta.JtaTransactionObject, org.springframework.transaction.TransactionDefinition)
,
JtaTransactionObject.getUserTransaction()
,
getTransactionManager()
protected void applyTimeout(JtaTransactionObject txObject, int timeout) throws SystemException
UserTransaction.setTransactionTimeout
for a non-default timeout value.
txObject
- the JtaTransactionObject containing the UserTransactiontimeout
- timeout value taken from transaction definition
SystemException
- if thrown by the JTA implementationdoJtaBegin(org.springframework.transaction.jta.JtaTransactionObject, org.springframework.transaction.TransactionDefinition)
,
JtaTransactionObject.getUserTransaction()
,
UserTransaction.setTransactionTimeout(int)
protected Object doSuspend(Object transaction)
AbstractPlatformTransactionManager
The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported.
doSuspend
in class AbstractPlatformTransactionManager
transaction
- transaction object returned by doGetTransaction
AbstractPlatformTransactionManager.doResume(java.lang.Object, java.lang.Object)
protected Object doJtaSuspend(JtaTransactionObject txObject) throws SystemException
Can be overridden in subclasses, for specific JTA implementations.
txObject
- the JtaTransactionObject containing the UserTransaction
SystemException
- if thrown by JTA methodsgetTransactionManager()
,
TransactionManager.suspend()
protected void doResume(Object transaction, Object suspendedResources)
AbstractPlatformTransactionManager
The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported.
doResume
in class AbstractPlatformTransactionManager
transaction
- transaction object returned by doGetTransaction
suspendedResources
- the object that holds suspended resources,
as returned by doSuspendAbstractPlatformTransactionManager.doSuspend(java.lang.Object)
protected void doJtaResume(JtaTransactionObject txObject, Object suspendedTransaction) throws InvalidTransactionException, SystemException
Can be overridden in subclasses, for specific JTA implementations.
txObject
- the JtaTransactionObject containing the UserTransactionsuspendedTransaction
- the suspended JTA Transaction object
InvalidTransactionException
- if thrown by JTA methods
SystemException
- if thrown by JTA methodsgetTransactionManager()
,
TransactionManager.resume(javax.transaction.Transaction)
protected boolean shouldCommitOnGlobalRollbackOnly()
shouldCommitOnGlobalRollbackOnly
in class AbstractPlatformTransactionManager
AbstractPlatformTransactionManager.doCommit(org.springframework.transaction.support.DefaultTransactionStatus)
,
DefaultTransactionStatus.isGlobalRollbackOnly()
,
AbstractTransactionStatus.isLocalRollbackOnly()
,
TransactionStatus.setRollbackOnly()
,
UnexpectedRollbackException
,
UserTransaction.commit()
,
RollbackException
protected void doCommit(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
An implementation does not need to check the "new transaction" flag or the rollback-only flag; this will already have been handled before. Usually, a straight commit will be performed on the transaction object contained in the passed-in status.
doCommit
in class AbstractPlatformTransactionManager
status
- the status representation of the transactionDefaultTransactionStatus.getTransaction()
protected void doRollback(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
An implementation does not need to check the "new transaction" flag; this will already have been handled before. Usually, a straight rollback will be performed on the transaction object contained in the passed-in status.
doRollback
in class AbstractPlatformTransactionManager
status
- the status representation of the transactionDefaultTransactionStatus.getTransaction()
protected void doSetRollbackOnly(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
The default implementation throws an IllegalTransactionStateException, assuming that participating in existing transactions is generally not supported. Subclasses are of course encouraged to provide such support.
doSetRollbackOnly
in class AbstractPlatformTransactionManager
status
- the status representation of the transactionprotected void registerAfterCompletionWithExistingTransaction(Object transaction, List synchronizations)
AbstractPlatformTransactionManager
Invoked when the control of the Spring transaction manager and thus all Spring transaction synchronizations end, without the transaction being completed yet. This is for example the case when participating in an existing JTA or EJB CMT transaction.
The default implementation simply invokes the afterCompletion
methods
immediately, passing in "STATUS_UNKNOWN". This is the best we can do if there's no
chance to determine the actual outcome of the outer transaction.
registerAfterCompletionWithExistingTransaction
in class AbstractPlatformTransactionManager
transaction
- transaction object returned by doGetTransaction
synchronizations
- List of TransactionSynchronization objectsAbstractPlatformTransactionManager.invokeAfterCompletion(java.util.List, int)
,
TransactionSynchronization.afterCompletion(int)
,
TransactionSynchronization.STATUS_UNKNOWN
protected void doRegisterAfterCompletionWithJtaTransaction(JtaTransactionObject txObject, List synchronizations) throws RollbackException, SystemException
afterCompletion
on the given Spring TransactionSynchronizations.
Can be overridden in subclasses, for specific JTA implementations.
synchronizations
- List of TransactionSynchronization objects
RollbackException
- if thrown by JTA methods
SystemException
- if thrown by JTA methodsgetTransactionManager()
,
Transaction.registerSynchronization(javax.transaction.Synchronization)
,
AbstractPlatformTransactionManager.invokeAfterCompletion(java.util.List, int)
|
The Spring Framework | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |