org.springframework.test.context.transaction

Annotation Type TransactionConfiguration

@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.

Since:

2.5

Author:

Sam Brannen

See Also:

TransactionalTestExecutionListener, ContextConfiguration

Optional Element Summary

Optional Elements

Modifier and Type	Optional Element and Description
boolean	defaultRollback Should transactions be rolled back by default?
String	transactionManager The bean name of the PlatformTransactionManager that should be used to drive transactions.

Element Detail

transactionManager

public abstract String transactionManager

The bean name of the PlatformTransactionManager that should be used to drive 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:

1. There is only one bean of type PlatformTransactionManager in the test's ApplicationContext.
2. TransactionManagementConfigurer has been implemented to specify which PlatformTransactionManager bean should be used for annotation-driven transaction management.
3. The 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="...">.

Default:

""

defaultRollback

public abstract boolean defaultRollback

Should transactions be rolled back by default?

Default:

true