Using Annotations for Transaction Management
Currently, using annotations is the most common way to define transaction requirements in Spring. The
main benefit is that the transaction requirement, together with the detail transaction properties
(timeout, isolation level, propagation behavior, and so on), were defined within the code itself, which
makes the application easier to trace and maintain.
To enable annotation support for transaction management in Spring, we need to add the
<tx:annotation-driven> tag in the XML configuration file. Listing 13-9 shows the configuration file
(tx-annotation-app-context.xml).
Listing 13-9. Spring Configuration for Annotation Transaction Support
<?xml version="1.0" encoding="UTF-8"?>
<jdbc:embedded-database id="dataSource" type="H2">
<jdbc:script location="classpath:schema.sql"/>
<jdbc:script location="classpath:test-data.sql"/>
</jdbc:embedded-database>
<bean id="transactionManager" class="org.springframework.orm.jpa.JpaTransactionManager">
<property name="entityManagerFactory" ref="emf"/>
</bean>
<tx:annotation-driven/>
<bean id="emf" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="dataSource" />
<property name="jpaVendorAdapter">
<bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter" />
</property>
<property name="packagesToScan" value="com.apress.prospring3.ch13.domain"/>
<property name="jpaProperties">
<props>
<prop key="hibernate.dialect">
org.hibernate.dialect.H2Dialect
</prop>
<prop key="hibernate.max_fetch_depth">3</prop>
<prop key="hibernate.jdbc.fetch_size">50</prop>
Search WWH :
