TransactionProxyFactoryBean when switching from configuration-based Service beans to annotation based service beans

Question

Hi guys,

I read about using

  <context:component-scan base-package="tld.mydomain.business">
      <context:include-filter type="annotation" expression="org.springframework.stereotype.Service"/>
  </context:component-scan>

and annotate my service beans with @Service("myService"), and thought great, I'll do that, since I'm already doing that with my controllers. My usual service bean configuration looks like

  <bean id="userService" parent="txProxyTemplate">
    <property name="target">
      <bean class="tld.mydomain.business.UserServiceImpl"/>
    </property>
    <property name="proxyInterfaces" value="tld.mydomain.business.UserService"/>
  </bean>

so now that I generate them, how do I wrap them in a Hibernate proxy such as TransactionProxyFactoryBean? Or is there a better way to do that as well?

I have not yet gone all the way and used @Repository as well, is that required?

Cheers

Nik

Answer 1

Using TransactionProxyFactoryBean is not encouraged in modern Spring applications, although it still works. The typical approach nowadays is to annotate classes with @Transactional, and then stick this element in your application context file:

<tx:annotation-driven transaction-manager="txManager"/>

This and other strategies are discussed in great depth in the reference document, and there's even a side note about TransactionProxyFactoryBean.

Answer 2

There's no need for

<context:include-filter type="annotation"expression="org.springframework.stereotype.Service"/>

Spring will register @Service, @Repository, @Component... once they are found in the base package.

Like @Rob said either use @Transactional or <aop:config>...</aop:config> to handle your transactions at the service level.

Answer 3

If you have two different resources that need to be in the same transaction, then you will need to use JTA. See my answer to an earlier question here. Your config would need to look something like:

<tx:annotation-driven transaction-manager="txManager"/>

<bean id="txManager" 
    class="org.springframework.transaction.jta.JtaTransactionManager">
    <property name="transactionManagerName" value="appserver/jndi/path" />
</bean>

Where appserver/jndi/path would need to be replaced with the JNDI path of the JTA transaction manager that comes with your application server (although you can use a standalone JTA transaction manager such as JOTM as well). Typical paths as mentioned in the 2.5.x API are:

• "java:comp/UserTransaction" for Resin 2.x, Oracle OC4J (Orion), JOnAS (JOTM), BEA WebLogic
• "java:comp/TransactionManager" for Resin 3.x
• "java:appserver/TransactionManager" for GlassFish
• "java:pm/TransactionManager" for Borland Enterprise Server and Sun Application Server (Sun ONE 7 and later)
• "java:/TransactionManager" for JBoss Application Server