Spring Framework 6.1.4 · org.springframework.transaction.annotation.Propagation

Field Summary

Modifier and Type	Field and Description
public static final Propagation	MANDATORY Support a current transaction, throw an exception if none exists.
public static final Propagation	NESTED Execute within a nested transaction if a current transaction exists, behave like `REQUIRED` otherwise.
public static final Propagation	NEVER Execute non-transactionally, throw an exception if a transaction exists.
public static final Propagation	NOT_SUPPORTED Execute non-transactionally, suspend the current transaction if one exists.
public static final Propagation	REQUIRED Support a current transaction, create a new one if none exists.
public static final Propagation	REQUIRES_NEW Create a new transaction, and suspend the current transaction if one exists.
public static final Propagation	SUPPORTS Support a current transaction, execute non-transactionally if none exists.
private final int	value

Access	Constructor and Description
private	Propagation(int value)

Modifier and Type	Method and Description
public int	value()
public static Propagation	valueOf(String name)
public static Propagation[]	values()

Field Detail

MANDATORY	back to summary
public static final Propagation MANDATORY Support a current transaction, throw an exception if none exists. Analogous to EJB transaction attribute of the same name.

NESTED back to summary

NESTED	back to summary
public static final Propagation NESTED Execute within a nested transaction if a current transaction exists, behave like `REQUIRED` otherwise. There is no analogous feature in EJB. Note Actual creation of a nested transaction will only work on specific transaction managers. Out of the box, this only applies to the JDBC DataSourceTransactionManager. Some JTA providers might support nested transactions as well. See Also `org.springframework.jdbc.datasource.DataSourceTransactionManager`

public static final Propagation NESTED

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

Note

Actual creation of a nested transaction will only work on specific transaction managers. Out of the box, this only applies to the JDBC DataSourceTransactionManager. Some JTA providers might support nested transactions as well.

See Also: org.springframework.jdbc.datasource.DataSourceTransactionManager

NEVER	back to summary
public static final Propagation NEVER Execute non-transactionally, throw an exception if a transaction exists. Analogous to EJB transaction attribute of the same name.

NOT_SUPPORTED back to summary

NOT_SUPPORTED	back to summary
public static final Propagation NOT_SUPPORTED Execute non-transactionally, suspend the current transaction if one exists. Analogous to EJB transaction attribute of the same name. Note Actual transaction suspension will not work out-of-the-box on all transaction managers. This in particular applies to `org.springframework.transaction.jta.JtaTransactionManager`, which requires the `jakarta.transaction.TransactionManager` to be made available to it (which is server-specific in standard Jakarta EE). See Also `org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager`

public static final Propagation NOT_SUPPORTED

Execute non-transactionally, suspend the current transaction if one exists. Analogous to EJB transaction attribute of the same name.

Note

Actual transaction suspension will not work out-of-the-box on all transaction managers. This in particular applies to org.springframework.transaction.jta.JtaTransactionManager, which requires the jakarta.transaction.TransactionManager to be made available to it (which is server-specific in standard Jakarta EE).

See Also: org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager

REQUIRED	back to summary
public static final Propagation REQUIRED Support a current transaction, create a new one if none exists. Analogous to EJB transaction attribute of the same name. This is the default setting of a transaction annotation.

REQUIRED

back to summary

public static final Propagation REQUIRED

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

This is the default setting of a transaction annotation.

REQUIRES_NEW back to summary

REQUIRES_NEW	back to summary
public static final Propagation REQUIRES_NEW Create a new transaction, and suspend the current transaction if one exists. Analogous to the EJB transaction attribute of the same name. Note Actual transaction suspension will not work out-of-the-box on all transaction managers. This in particular applies to `org.springframework.transaction.jta.JtaTransactionManager`, which requires the `jakarta.transaction.TransactionManager` to be made available to it (which is server-specific in standard Jakarta EE). See Also `org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager`

public static final Propagation REQUIRES_NEW

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

Note

See Also: org.springframework.transaction.jta.JtaTransactionManager#setTransactionManager

SUPPORTS back to summary

SUPPORTS	back to summary
public static final Propagation SUPPORTS Support a current transaction, execute non-transactionally if none exists. Analogous to EJB transaction attribute of the same name. Note For transaction managers with transaction synchronization, `SUPPORTS` is slightly different from no transaction at all, as it defines a transaction scope that synchronization will apply for. As a consequence, the same resources (JDBC Connection, Hibernate Session, etc) will be shared for the entire specified scope. Note that this depends on the actual synchronization configuration of the transaction manager. See Also `org.springframework.transaction.support.AbstractPlatformTransactionManager#setTransactionSynchronization`

public static final Propagation SUPPORTS

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

Note

For transaction managers with transaction synchronization, SUPPORTS is slightly different from no transaction at all, as it defines a transaction scope that synchronization will apply for. As a consequence, the same resources (JDBC Connection, Hibernate Session, etc) will be shared for the entire specified scope. Note that this depends on the actual synchronization configuration of the transaction manager.

See Also: org.springframework.transaction.support.AbstractPlatformTransactionManager#setTransactionSynchronization

value	back to summary
private final int value

public final Enum Propagation

Field Summary

Constructor Summary

Method Summary

Field Detail

Constructor Detail

Method Detail