So in the latest version of Spring we are able to use the @Configuration
annotation to setup our configurations for Spring. Now in JavaConfig it is possible to
You can now use @EnableTransactionManagement
.
See this post for more details: http://blog.springsource.com/2011/06/10/spring-3-1-m2-configuration-enhancements/
Take a look at http://blog.springsource.com/2011/02/17/spring-3-1-m1-featurespec. Spring 3.1's FeatureSpecification classes such as TxAnnotationDriven are designed to solve exactly the problem described above.
It seems like it isn't possible according to this forum post:
there may be a more first-class mechanism for enabling annotation-driven TX in
@Configuration
classes in Spring 3.1, but in the meantime, the recommended approach is to use@ImportResource
to include a snippet of XML that declares<tx:annotation-driven/>
Wait: but you seem to have an XML context anyway. Why not add <tx:annotation-driven/>
to it and use @Transactional?