|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||
java.lang.Objectorg.springframework.transaction.support.AbstractPlatformTransactionManager
org.springframework.jdbc.datasource.DataSourceTransactionManager
PlatformTransactionManager implementation for a single JDBC DataSource. Binds a JDBC connection from the specified DataSource to the thread, potentially allowing for one thread connection per data source.
Application code is required to retrieve the JDBC Connection via
DataSourceUtils.getConnection(DataSource) instead of J2EE's standard
DataSource.getConnection(). This is recommended anyway, as it throws
unchecked org.springframework.dao exceptions instead of checked SQLException.
All framework classes like JdbcTemplate use this strategy implicitly.
If not used with this transaction manager, the lookup strategy behaves exactly
like the common one - it can thus be used in any case.
Alternatively, you can also allow application code to work with the standard
J2EE lookup pattern DataSource.getConnection(), for example for
legacy code that is not aware of Spring at all. In that case, define a
TransactionAwareDataSourceProxy for your target DataSource, and pass that proxy
DataSource to your DAOs, which will automatically participate in Spring-managed
transactions through it. Note that DataSourceTransactionManager still needs to
be wired with the target DataSource, driving transactions for it.
Supports custom isolation levels, and timeouts that get applied as
appropriate JDBC statement query timeouts. To support the latter,
application code must either use JdbcTemplate or call
DataSourceUtils.applyTransactionTimeout for each created statement.
On JDBC 3.0, this transaction manager supports nested transactions via JDBC 3.0 Savepoints. The "nestedTransactionAllowed" flag defaults to true, as nested transactions work without restrictions on JDBC drivers that support Savepoints (like Oracle).
This implementation can be used instead of JtaTransactionManager in the single resource case, as it does not require the container to support JTA: typically, in combination with a locally defined JDBC DataSource like a Jakarta Commons DBCP connection pool. Switching between this local strategy and a JTA environment is just a matter of configuration, if you stick to the required connection lookup pattern. Note that JTA does not support custom isolation levels!
AbstractPlatformTransactionManager.setNestedTransactionAllowed(boolean),
Savepoint,
DataSourceUtils.getConnection(javax.sql.DataSource),
DataSourceUtils.applyTransactionTimeout(java.sql.Statement, javax.sql.DataSource),
DataSourceUtils.closeConnectionIfNecessary(java.sql.Connection, javax.sql.DataSource),
TransactionAwareDataSourceProxy,
JdbcTemplate,
Serialized Form| Field Summary |
| Fields inherited from class org.springframework.transaction.support.AbstractPlatformTransactionManager |
logger, SYNCHRONIZATION_ALWAYS, SYNCHRONIZATION_NEVER, SYNCHRONIZATION_ON_ACTUAL_TRANSACTION |
| Constructor Summary | |
DataSourceTransactionManager()
Create a new DataSourceTransactionManager instance. |
|
DataSourceTransactionManager(javax.sql.DataSource dataSource)
Create a new DataSourceTransactionManager instance. |
|
| Method Summary | |
void |
afterPropertiesSet()
Invoked by a BeanFactory after it has set all bean properties supplied (and satisfied BeanFactoryAware and ApplicationContextAware). |
protected void |
doBegin(java.lang.Object transaction,
TransactionDefinition definition)
This implementation sets the isolation level but ignores the timeout. |
protected void |
doCleanupAfterCompletion(java.lang.Object transaction)
Cleanup resources after transaction completion. |
protected void |
doCommit(DefaultTransactionStatus status)
Perform an actual commit on the given transaction. |
protected java.lang.Object |
doGetTransaction()
Return a current transaction object, i.e. a JTA UserTransaction. |
protected void |
doResume(java.lang.Object transaction,
java.lang.Object suspendedResources)
Resume the resources of the current transaction. |
protected void |
doRollback(DefaultTransactionStatus status)
Perform an actual rollback on the given transaction. |
protected void |
doSetRollbackOnly(DefaultTransactionStatus status)
Set the given transaction rollback-only. |
protected java.lang.Object |
doSuspend(java.lang.Object transaction)
Suspend the resources of the current transaction. |
javax.sql.DataSource |
getDataSource()
Return the JDBC DataSource that this instance manages transactions for. |
protected boolean |
isExistingTransaction(java.lang.Object transaction)
Check if the given transaction object indicates an existing, i.e. already begun, transaction. |
void |
setDataSource(javax.sql.DataSource dataSource)
Set the JDBC DataSource that this instance should manage transactions for. |
| Methods inherited from class org.springframework.transaction.support.AbstractPlatformTransactionManager |
commit, getTransaction, getTransactionSynchronization, isNestedTransactionAllowed, isRollbackOnCommitFailure, rollback, setNestedTransactionAllowed, setRollbackOnCommitFailure, setTransactionSynchronization, setTransactionSynchronizationName, useSavepointForNestedTransaction |
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
public DataSourceTransactionManager()
setDataSource(javax.sql.DataSource)public DataSourceTransactionManager(javax.sql.DataSource dataSource)
dataSource - JDBC DataSource to manage transactions for| Method Detail |
public void setDataSource(javax.sql.DataSource dataSource)
This will typically be a locally defined DataSource, for example a Jakarta Commons DBCP connection pool. Alternatively, you can also drive transactions for a non-XA J2EE DataSource fetched from JNDI. For an XA DataSource, use JtaTransactionManager.
JtaTransactionManagerpublic javax.sql.DataSource getDataSource()
public void afterPropertiesSet()
InitializingBeanThis method allows the bean instance to perform initialization only possible when all bean properties have been set and to throw an exception in the event of misconfiguration.
afterPropertiesSet in interface InitializingBeanprotected java.lang.Object doGetTransaction()
AbstractPlatformTransactionManager
doGetTransaction in class AbstractPlatformTransactionManagerprotected boolean isExistingTransaction(java.lang.Object transaction)
AbstractPlatformTransactionManager
isExistingTransaction in class AbstractPlatformTransactionManagertransaction - transaction object returned by doGetTransaction
protected void doBegin(java.lang.Object transaction,
TransactionDefinition definition)
doBegin in class AbstractPlatformTransactionManagertransaction - transaction object returned by doGetTransactiondefinition - TransactionDefinition instance, describing
propagation behavior, isolation level, timeout etc.protected java.lang.Object doSuspend(java.lang.Object transaction)
AbstractPlatformTransactionManager
doSuspend in class AbstractPlatformTransactionManagertransaction - transaction object returned by doGetTransaction
AbstractPlatformTransactionManager.doResume(java.lang.Object, java.lang.Object)
protected void doResume(java.lang.Object transaction,
java.lang.Object suspendedResources)
AbstractPlatformTransactionManager
doResume in class AbstractPlatformTransactionManagertransaction - transaction object returned by doGetTransactionsuspendedResources - the object that holds suspended resources,
as returned by doSuspendAbstractPlatformTransactionManager.doSuspend(java.lang.Object)protected void doCommit(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
doCommit in class AbstractPlatformTransactionManagerstatus - status representation of the transactionprotected void doRollback(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
doRollback in class AbstractPlatformTransactionManagerstatus - status representation of the transactionprotected void doSetRollbackOnly(DefaultTransactionStatus status)
AbstractPlatformTransactionManager
doSetRollbackOnly in class AbstractPlatformTransactionManagerstatus - status representation of the transactionprotected void doCleanupAfterCompletion(java.lang.Object transaction)
AbstractPlatformTransactionManagerDefault implementation does nothing.
doCleanupAfterCompletion in class AbstractPlatformTransactionManagertransaction - transaction object returned by doGetTransaction
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||