注释类型 EnableTransactionManagement
@Target(TYPE) @Retention(RUNTIME) @Documented @Import(TransactionManagementConfigurationSelector.class) public @interface EnableTransactionManagement
Enables Spring's annotation-driven transaction management capability, similar to the support found in Spring's<tx:*>
XML namespace. To be used on@Configuration
classes as follows:@Configuration @EnableTransactionManagement public class AppConfig { @Bean public FooRepository fooRepository() { // configure and return a class having @Transactional methods return new JdbcFooRepository(dataSource()); } @Bean public DataSource dataSource() { // configure and return the necessary JDBC DataSource } @Bean public PlatformTransactionManager txManager() { return new DataSourceTransactionManager(dataSource()); } }
For reference, the example above can be compared to the following Spring XML configuration:
<beans> <tx:annotation-driven/> <bean id="fooRepository" class="com.foo.JdbcFooRepository"> <constructor-arg ref="dataSource"/> </bean> <bean id="dataSource" class="com.vendor.VendorDataSource"/> <bean id="transactionManager" class="org.sfwk...DataSourceTransactionManager"> <constructor-arg ref="dataSource"/> </bean> </beans>
@EnableTransactionManagement
and<tx:annotation-driven/>
are responsible for registering the necessary Spring components that power annotation-driven transaction management, such as the TransactionInterceptor and the proxy- or AspectJ-based advice that weave the interceptor into the call stack whenJdbcFooRepository
's@Transactional
methods are invoked.A minor difference between the two examples lies in the naming of the
PlatformTransactionManager
bean: In the@Bean
case, the name is "txManager" (per the name of the method); in the XML case, the name is "transactionManager". The<tx:annotation-driven/>
is hard-wired to look for a bean named "transactionManager" by default, however@EnableTransactionManagement
is more flexible; it will fall back to a by-type lookup for anyPlatformTransactionManager
bean in the container. Thus the name can be "txManager", "transactionManager", or "tm": it simply does not matter.For those that wish to establish a more direct relationship between
@EnableTransactionManagement
and the exact transaction manager bean to be used, theTransactionManagementConfigurer
callback interface may be implemented - notice theimplements
clause and the@Override
-annotated method below:@Configuration @EnableTransactionManagement public class AppConfig implements TransactionManagementConfigurer { @Bean public FooRepository fooRepository() { // configure and return a class having @Transactional methods return new JdbcFooRepository(dataSource()); } @Bean public DataSource dataSource() { // configure and return the necessary JDBC DataSource } @Bean public PlatformTransactionManager txManager() { return new DataSourceTransactionManager(dataSource()); } @Override public PlatformTransactionManager annotationDrivenTransactionManager() { return txManager(); } }
This approach may be desirable simply because it is more explicit, or it may be necessary in order to distinguish between twoPlatformTransactionManager
beans present in the same container. As the name suggests, theannotationDrivenTransactionManager()
will be the one used for processing@Transactional
methods. SeeTransactionManagementConfigurer
Javadoc for further details.The
mode()
attribute controls how advice is applied: If the mode isAdviceMode.PROXY
(the default), then the other attributes control the behavior of the proxying. Please note that proxy mode allows for interception of calls through the proxy only; local calls within the same class cannot get intercepted that way.Note that if the mode() is set to
AdviceMode.ASPECTJ
, then the value of theproxyTargetClass()
attribute will be ignored. Note also that in this case thespring-aspects
module JAR must be present on the classpath, with compile-time weaving or load-time weaving applying the aspect to the affected classes. There is no proxy involved in such a scenario; local calls will be intercepted as well.- 从以下版本开始:
- 3.1
- 作者:
- Chris Beams, Juergen Hoeller
- 另请参阅:
TransactionManagementConfigurer
,TransactionManagementConfigurationSelector
,ProxyTransactionManagementConfiguration
,AspectJTransactionManagementConfiguration
可选元素概要
可选元素 修饰符和类型 可选元素 说明 AdviceMode
mode
Indicate how transactional advice should be applied.int
order
Indicate the ordering of the execution of the transaction advisor when multiple advices are applied at a specific joinpoint.boolean
proxyTargetClass
Indicate whether subclass-based (CGLIB) proxies are to be created (true
) as opposed to standard Java interface-based proxies (false
).
元素详细资料
proxyTargetClass
boolean proxyTargetClass
Indicate whether subclass-based (CGLIB) proxies are to be created (true
) as opposed to standard Java interface-based proxies (false
). The default isfalse
. Applicable only ifmode()
is set toAdviceMode.PROXY
.Note that setting this attribute to
true
will affect all Spring-managed beans requiring proxying, not just those marked with@Transactional
. For example, other beans marked with Spring's@Async
annotation will be upgraded to subclass proxying at the same time. This approach has no negative impact in practice unless one is explicitly expecting one type of proxy vs another, e.g. in tests.- 默认值:
- false
mode
AdviceMode mode
Indicate how transactional advice should be applied.The default is
AdviceMode.PROXY
. Please note that proxy mode allows for interception of calls through the proxy only. Local calls within the same class cannot get intercepted that way; anTransactional
annotation on such a method within a local call will be ignored since Spring's interceptor does not even kick in for such a runtime scenario. For a more advanced mode of interception, consider switching this toAdviceMode.ASPECTJ
.- 默认值:
- org.springframework.context.annotation.AdviceMode.PROXY
order
int order
Indicate the ordering of the execution of the transaction advisor when multiple advices are applied at a specific joinpoint.The default is
Ordered.LOWEST_PRECEDENCE
.- 默认值:
- 2147483647