org.springframework.transaction.PlatformTransactionManager implementation
for a single JDBC javax.sql.DataSource . This class is capable of working
in any environment with any JDBC driver, as long as the setup uses a
javax.sql.DataSource as its Connection factory mechanism.
Binds a JDBC Connection from the specified DataSource to the
current thread, potentially allowing for one thread-bound Connection
per DataSource.Note
The DataSource that this transaction manager operates on
needs to return independent Connections. The Connections
typically come from a connection pool but the DataSource must not return
specifically scoped or constrained Connections. This transaction manager
will associate Connections with thread-bound transactions, according
to the specified propagation behavior. It assumes that a separate, independent
Connection can be obtained even during an ongoing transaction.
Application code is required to retrieve the JDBC Connection via
DataSourceUtils#getConnection(DataSource) instead of a standard
EE-style DataSource#getConnection() call. Spring classes such as
org. use this strategy implicitly.
If not used in combination with this transaction manager, the
DataSourceUtils lookup strategy behaves exactly like the native
DataSource lookup; it can thus be used in a portable fashion.
Alternatively, you can allow application code to work with the standard
EE-style 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 when accessing it.
Supports custom isolation levels, and timeouts which get applied as
appropriate JDBC statement timeouts. To support the latter, application code
must either use org., call
DataSourceUtils#applyTransactionTimeout for each created JDBC
Statement, or go through a TransactionAwareDataSourceProxy
which will create timeout-aware JDBC Connections and Statements
automatically.
Consider defining a LazyConnectionDataSourceProxy for your target
DataSource, pointing both this transaction manager and your DAOs to it.
This will lead to optimized handling of "empty" transactions, i.e. of transactions
without any JDBC statements executed. A LazyConnectionDataSourceProxy will
not fetch an actual JDBC Connection from the target DataSource
until a Statement gets executed, lazily applying the specified transaction
settings to the target Connection.
This transaction manager supports nested transactions via the JDBC
java. mechanism. The
"nestedTransactionAllowed" flag defaults
to "true", since nested transactions will work without restrictions on JDBC
drivers that support savepoints (such as the Oracle JDBC driver).
This transaction manager can be used as a replacement for the
org. in the single
resource case, as it does not require a container that supports JTA, typically
in combination with a locally defined JDBC DataSource (e.g. a Hikari
connection pool). Switching between this local strategy and a JTA environment
is just a matter of configuration!
As of 4.3.4, this transaction manager triggers flush callbacks on registered
transaction synchronizations (if synchronization is generally active), assuming
resources operating on the underlying JDBC Connection. This allows for
setup analogous to JtaTransactionManager, in particular with respect to
lazily registered ORM resources (e.g. a Hibernate Session).
NOTE: As of 5.3, org.
is available as an extended subclass which includes commit/rollback exception
translation, aligned with org..
setNestedTransactionAllowed, java.sql.Savepoint , DataSourceUtils#getConnection(javax.sql.DataSource) , DataSourceUtils#applyTransactionTimeout, DataSourceUtils#releaseConnection, TransactionAwareDataSourceProxy, LazyConnectionDataSourceProxy, org.springframework.jdbc.core.JdbcTemplate , org.springframework.jdbc.support.JdbcTransactionManager
| Modifier and Type | Class and Description |
|---|---|
| private static class | DataSourceTransactionManager.
DataSource transaction object, representing a ConnectionHolder. |
| Modifier and Type | Field and Description |
|---|---|
| private DataSource | |
| private boolean |
| Access | Constructor and Description |
|---|---|
| public | |
| public | DataSourceTransactionManager(DataSource
the JDBC DataSource to manage transactions for dataSource)Create a new |
| Modifier and Type | Method and Description |
|---|---|
| public void | afterPropertiesSet()
Implements org. Invoked by the containing This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set. |
| protected void | doBegin(Object
the transaction object returned by transaction, TransactionDefinition doGetTransactiona TransactionDefinition instance, describing propagation
behavior, isolation level, read-only flag, timeout, and transaction name definition)Implements abstract org. Begin a new transaction with semantics according to the given transaction definition. |
| protected void | doCleanupAfterCompletion(Object
the transaction object returned by transaction)doGetTransactionOverrides org. Cleanup resources after transaction completion. |
| protected void | doCommit(DefaultTransactionStatus
the status representation of the transaction status)Implements abstract org. Perform an actual commit of the given transaction. |
| protected Object | doGetTransaction()
Implements abstract org. Return a transaction object for the current transaction state. |
| protected void | doResume(Object
the transaction object returned by transaction, Object doGetTransactionthe object that holds suspended resources,
as returned by doSuspend suspendedResources)Overrides org. Resume the resources of the current transaction. |
| protected void | doRollback(DefaultTransactionStatus
the status representation of the transaction status)Implements abstract org. Perform an actual rollback of the given transaction. |
| protected void | doSetRollbackOnly(DefaultTransactionStatus
the status representation of the transaction status)Overrides org. Set the given transaction rollback-only. |
| protected Object | doSuspend(Object
the transaction object returned by transaction)doGetTransactionOverrides org. Suspend the resources of the current transaction. |
| public DataSource | |
| public Object | getResourceFactory()
Implements org. Return the resource factory that this transaction manager operates on, e.g. a JDBC DataSource or a JMS ConnectionFactory. |
| public boolean | isEnforceReadOnly()
Return whether to enforce the read-only nature of a transaction through an explicit statement on the transactional connection. |
| protected boolean | isExistingTransaction(Object
the transaction object returned by doGetTransaction transaction)Overrides org. Check if the given transaction object indicates an existing transaction (that is, a transaction which has already started). |
| protected DataSource | |
| protected void | prepareTransactionalConnection(Connection
the transactional JDBC Connection con, TransactionDefinition the current transaction definition definition)Prepare the transactional |
| public void | setDataSource(DataSource dataSource)
Set the JDBC |
| public void | setEnforceReadOnly(boolean enforceReadOnly)
Specify whether to enforce the read-only nature of a transaction
(as indicated by |
| protected RuntimeException | Returns: the translated exception to throw, either aorg. or a
org.the task description (commit or rollback) task, SQLException the SQLException thrown from commit/rollback ex)Translate the given JDBC commit/rollback exception to a common Spring
exception to propagate from the |
| dataSource | back to summary |
|---|---|
| private DataSource dataSource
| |
| enforceReadOnly | back to summary |
|---|---|
| private boolean enforceReadOnly | |
| DataSourceTransactionManager | back to summary |
|---|---|
| public DataSourceTransactionManager() Create a new
| |
| DataSourceTransactionManager | back to summary |
|---|---|
| public DataSourceTransactionManager(DataSource dataSource) Create a new
| |
| afterPropertiesSet | back to summary |
|---|---|
| public void afterPropertiesSet() Implements org. Doc from org. Invoked by the containing This method allows the bean instance to perform validation of its overall configuration and final initialization when all bean properties have been set.
| |
| doBegin | back to summary |
|---|---|
| protected void doBegin(Object transaction, TransactionDefinition definition) Implements abstract org. Doc from org. Begin a new transaction with semantics according to the given transaction definition. Does not have to care about applying the propagation behavior, as this has already been handled by this abstract manager. 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
| |
| doCleanupAfterCompletion | back to summary |
|---|---|
| protected void doCleanupAfterCompletion(Object transaction) Overrides org. Doc from org. Cleanup resources after transaction completion. Called after Should not throw any exceptions but just issue warnings on errors. | |
| doCommit | back to summary |
|---|---|
| protected void doCommit(DefaultTransactionStatus status) Implements abstract org. Doc from org. Perform an actual commit of the given transaction. 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.
| |
| doGetTransaction | back to summary |
|---|---|
| protected Object doGetTransaction() Implements abstract org. Doc from org. Return a transaction object for the current transaction state. The returned object will usually be specific to the concrete transaction manager implementation, carrying corresponding transaction state in a modifiable fashion. This object will be passed into the other template methods (e.g. doBegin and doCommit), either directly or as part of a DefaultTransactionStatus instance. The returned object should contain information about any existing
transaction, that is, a transaction that has already started before the
current | |
| doResume | back to summary |
|---|---|
| protected void doResume(Object transaction, Object suspendedResources) Overrides org. Doc from org. Resume the resources of the current transaction. Transaction synchronization will be resumed afterwards. The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported. | |
| doRollback | back to summary |
|---|---|
| protected void doRollback(DefaultTransactionStatus status) Implements abstract org. Doc from org. Perform an actual rollback of the given transaction. 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.
| |
| doSetRollbackOnly | back to summary |
|---|---|
| protected void doSetRollbackOnly(DefaultTransactionStatus status) Overrides org. Doc from org. Set the given transaction rollback-only. Only called on rollback if the current transaction participates in an existing one. 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.
| |
| doSuspend | back to summary |
|---|---|
| protected Object doSuspend(Object transaction) Overrides org. Doc from org. Suspend the resources of the current transaction. Transaction synchronization will already have been suspended. The default implementation throws a TransactionSuspensionNotSupportedException, assuming that transaction suspension is generally not supported. | |
| getDataSource | back to summary |
|---|---|
| public DataSource getDataSource() Return the JDBC
| |
| getResourceFactory | back to summary |
|---|---|
| public Object getResourceFactory() Implements org. Doc from org. Return the resource factory that this transaction manager operates on, e.g. a JDBC DataSource or a JMS ConnectionFactory. This target resource factory is usually used as resource key for
| |
| isEnforceReadOnly | back to summary |
|---|---|
| public boolean isEnforceReadOnly() Return whether to enforce the read-only nature of a transaction through an explicit statement on the transactional connection.
| |
| isExistingTransaction | back to summary |
|---|---|
| protected boolean isExistingTransaction(Object transaction) Overrides org. Doc from org. Check if the given transaction object indicates an existing transaction (that is, a transaction which has already started). 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 | |
| obtainDataSource | back to summary |
|---|---|
| protected DataSource obtainDataSource() Obtain the
| |
| prepareTransactionalConnection | back to summary |
|---|---|
| protected void prepareTransactionalConnection(Connection con, TransactionDefinition definition) throws SQLException Prepare the transactional The default implementation executes a "SET TRANSACTION READ ONLY" statement
if the The "SET TRANSACTION READ ONLY" is understood by Oracle, MySQL and Postgres and may work with other databases as well. If you'd like to adapt this treatment, override this method accordingly.
| |
| setDataSource | back to summary |
|---|---|
| public void setDataSource(DataSource dataSource) Set the JDBC This will typically be a locally defined The The
| |
| setEnforceReadOnly | back to summary |
|---|---|
| public void setEnforceReadOnly(boolean enforceReadOnly) Specify whether to enforce the read-only nature of a transaction
(as indicated by The exact treatment, including any SQL statement executed on the connection,
can be customized through This mode of read-only handling goes beyond the Note that older Oracle JDBC drivers (9i, 10g) used to enforce this read-only
mode even for
| |
| translateException | back to summary |
|---|---|
| protected RuntimeException translateException(String task, SQLException ex) Translate the given JDBC commit/rollback exception to a common Spring
exception to propagate from the The default implementation throws a
| |
| Modifier and Type | Field and Description |
|---|---|
| private boolean | |
| private boolean |
| Access | Constructor and Description |
|---|---|
| private |
| Modifier and Type | Method and Description |
|---|---|
| public void | flush()
Overrides default org. Flush the underlying sessions to the datastore, if applicable: for example, all affected Hibernate/JPA sessions. |
| public boolean | |
| public boolean | |
| public boolean | isRollbackOnly()
Overrides default org. Return whether the transaction is internally marked as rollback-only. |
| public void | |
| public void | |
| public void |
| mustRestoreAutoCommit | back to summary |
|---|---|
| private boolean mustRestoreAutoCommit | |
| newConnectionHolder | back to summary |
|---|---|
| private boolean newConnectionHolder | |
| DataSourceTransactionObject | back to summary |
|---|---|
| private DataSourceTransactionObject() | |
| flush | back to summary |
|---|---|
| public void flush() Overrides default org. Doc from org. Flush the underlying sessions to the datastore, if applicable: for example, all affected Hibernate/JPA sessions. The default implementation is empty, considering flush as a no-op.
| |
| isMustRestoreAutoCommit | back to summary |
|---|---|
| public boolean isMustRestoreAutoCommit() | |
| isNewConnectionHolder | back to summary |
|---|---|
| public boolean isNewConnectionHolder() | |
| isRollbackOnly | back to summary |
|---|---|
| public boolean isRollbackOnly() Overrides default org. Doc from org. Return whether the transaction is internally marked as rollback-only. Can, for example, check the JTA UserTransaction. The default implementation returns
| |
| setConnectionHolder | back to summary |
|---|---|
| public void setConnectionHolder(ConnectionHolder connectionHolder, boolean newConnectionHolder) | |
| setMustRestoreAutoCommit | back to summary |
|---|---|
| public void setMustRestoreAutoCommit(boolean mustRestoreAutoCommit) | |
| setRollbackOnly | back to summary |
|---|---|
| public void setRollbackOnly() | |