@Rollback at the class
level and the transactionManager qualifier in @Transactional.@Deprecated @Documented @Inherited @Retention(value=RUNTIME) @Target(value=TYPE) public @interface TransactionConfiguration
TransactionConfiguration defines class-level metadata for configuring
transactional tests.
As of Spring Framework 4.0, this annotation may be used as a meta-annotation to create custom composed annotations.
TransactionalTestExecutionListener,
Transactional,
Commit,
Rollback,
Sql,
SqlConfig,
SqlConfig.transactionManager(),
ContextConfiguration| Modifier and Type | Optional Element and Description |
|---|---|
boolean |
defaultRollback
Deprecated.
Whether test-managed transactions should be rolled back by default.
|
String |
transactionManager
Deprecated.
The bean name of the
PlatformTransactionManager that should be used to drive test-managed transactions. |
public abstract String transactionManager
PlatformTransactionManager that should be used to drive test-managed transactions.
The name is only used if there is more than one bean of type
PlatformTransactionManager in the test's ApplicationContext.
If there is only one such bean, it is not necessary to specify a bean name.
Defaults to an empty string, requiring that one of the following is true:
PlatformTransactionManager in
the test's ApplicationContext.TransactionManagementConfigurer has been implemented to specify which
PlatformTransactionManager bean should be used for annotation-driven
transaction management.PlatformTransactionManager to use is named
"transactionManager".NOTE: The XML <tx:annotation-driven> element also refers
to a bean named "transactionManager" by default. If you are using both
features in combination, make sure to point to the same transaction manager
bean — here in @TransactionConfiguration and also in
<tx:annotation-driven transaction-manager="...">.