public Interface TransactionDefinition

Use the default isolation level of the underlying datastore.

All other levels correspond to the JDBC isolation levels.

See Also

java.sql.Connection

Indicates that dirty reads are prevented; non-repeatable reads and phantom reads can occur.

This level only prohibits a transaction from reading a row with uncommitted changes in it.

See Also

java.sql.Connection#TRANSACTION_READ_COMMITTED

Indicates that dirty reads, non-repeatable reads, and phantom reads can occur.

This level allows a row changed by one transaction to be read by another transaction before any changes in that row have been committed (a "dirty read"). If any of the changes are rolled back, the second transaction will have retrieved an invalid row.

See Also

java.sql.Connection#TRANSACTION_READ_UNCOMMITTED

Indicates that dirty reads and non-repeatable reads are prevented; phantom reads can occur.

This level prohibits a transaction from reading a row with uncommitted changes in it, and it also prohibits the situation where one transaction reads a row, a second transaction alters the row, and the first transaction re-reads the row, getting different values the second time (a "non-repeatable read").

See Also

java.sql.Connection#TRANSACTION_REPEATABLE_READ

Indicates that dirty reads, non-repeatable reads, and phantom reads are prevented.

This level includes the prohibitions in ISOLATION_REPEATABLE_READ and further prohibits the situation where one transaction reads all rows that satisfy a WHERE condition, a second transaction inserts a row that satisfies that WHERE condition, and the first transaction re-reads for the same condition, retrieving the additional "phantom" row in the second read.

See Also

java.sql.Connection#TRANSACTION_SERIALIZABLE

Support a current transaction; throw an exception if no current transaction exists. Analogous to the EJB transaction attribute of the same name.

Note that transaction synchronization within a PROPAGATION_MANDATORY scope will always be driven by the surrounding transaction.

Execute within a nested transaction if a current transaction exists, behaving like PROPAGATION_REQUIRED otherwise. There is no analogous feature in EJB.

See Also

org.springframework.jdbc.datasource.DataSourceTransactionManager

Do not support a current transaction; throw an exception if a current transaction exists. Analogous to the EJB transaction attribute of the same name.

Note that transaction synchronization is not available within a PROPAGATION_NEVER scope.

Do not support a current transaction; rather always execute non-transactionally. Analogous to the EJB transaction attribute of the same name.

Note that transaction synchronization is not available within a PROPAGATION_NOT_SUPPORTED scope. Existing synchronizations will be suspended and resumed appropriately.

See Also

org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager

Support a current transaction; create a new one if none exists. Analogous to the EJB transaction attribute of the same name.

This is typically the default setting of a transaction definition and typically defines a transaction synchronization scope.

Create a new transaction, suspending the current transaction if one exists. Analogous to the EJB transaction attribute of the same name.

A PROPAGATION_REQUIRES_NEW scope always defines its own transaction synchronizations. Existing synchronizations will be suspended and resumed appropriately.

See Also

org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager

Support a current transaction; execute non-transactionally if none exists. Analogous to the EJB transaction attribute of the same name.

In general, use PROPAGATION_SUPPORTS with care. In particular, do not rely on PROPAGATION_REQUIRED or PROPAGATION_REQUIRES_NEW within a PROPAGATION_SUPPORTS scope (which may lead to synchronization conflicts at runtime). If such nesting is unavoidable, make sure to configure your transaction manager appropriately (typically switching to "synchronization on actual transaction").

See Also

org.springframework.transaction.support.AbstractPlatformTransactionManager#setTransactionSynchronization, org.springframework.transaction.support.AbstractPlatformTransactionManager#SYNCHRONIZATION_ON_ACTUAL_TRANSACTION

Use the default timeout of the underlying transaction system, or none if timeouts are not supported.

Return the isolation level.

Must return one of the ISOLATION_XXX constants defined on this interface. Those constants are designed to match the values of the same constants on java.sql.Connection.

Exclusively designed for use with PROPAGATION_REQUIRED or PROPAGATION_REQUIRES_NEW since it only applies to newly started transactions. Consider switching the "validateExistingTransactions" flag to "true" on your transaction manager if you'd like isolation level declarations to get rejected when participating in an existing transaction with a different isolation level.

The default is ISOLATION_DEFAULT. Note that a transaction manager that does not support custom isolation levels will throw an exception when given any other level than ISOLATION_DEFAULT.

Returns:int

the isolation level

See Also

ISOLATION_DEFAULT, org.springframework.transaction.support.AbstractPlatformTransactionManager#setValidateExistingTransaction

Return the name of this transaction. Can be null.

This will be used as the transaction name to be shown in a transaction monitor, if applicable.

In case of Spring's declarative transactions, the exposed name will be the fully-qualified class name + "." + method name (by default).

Returns:String

the name of this transaction (null by default}

Annotations

@Nullable

See Also

org.springframework.transaction.interceptor.TransactionAspectSupport, org.springframework.transaction.support.TransactionSynchronizationManager#getCurrentTransactionName()

Return the propagation behavior.

Must return one of the PROPAGATION_XXX constants defined on this interface.

The default is PROPAGATION_REQUIRED.

Returns:int

the propagation behavior

See Also

PROPAGATION_REQUIRED, org.springframework.transaction.support.TransactionSynchronizationManager#isActualTransactionActive()

Return the transaction timeout.

Must return a number of seconds, or TIMEOUT_DEFAULT.

Exclusively designed for use with PROPAGATION_REQUIRED or PROPAGATION_REQUIRES_NEW since it only applies to newly started transactions.

Note that a transaction manager that does not support timeouts will throw an exception when given any other timeout than TIMEOUT_DEFAULT.

The default is TIMEOUT_DEFAULT.

Returns:int

the transaction timeout

Return whether to optimize as a read-only transaction.

The read-only flag applies to any transaction context, whether backed by an actual resource transaction (PROPAGATION_REQUIRED/ PROPAGATION_REQUIRES_NEW) or operating non-transactionally at the resource level (PROPAGATION_SUPPORTS). In the latter case, the flag will only apply to managed resources within the application, such as a Hibernate Session.

This just serves as a hint for the actual transaction subsystem; it will not necessarily cause failure of write access attempts. A transaction manager which cannot interpret the read-only hint will not throw an exception when asked for a read-only transaction.

Returns:boolean

true if the transaction is to be optimized as read-only (false by default)

See Also

org.springframework.transaction.support.TransactionSynchronization#beforeCommit(boolean), org.springframework.transaction.support.TransactionSynchronizationManager#isCurrentTransactionReadOnly()

Return an unmodifiable TransactionDefinition with defaults.

For customization purposes, use the modifiable org.springframework.transaction.support.DefaultTransactionDefinition instead.

Since

5.2