Add support for multiple TransactionManagers using @Transactional annotation [SPR-5896]

[spring-projects-issues]

Tom Spencer opened SPR-5896 and commented

It would be great to have support for using the @Transactional annotation in a multipe TransactionManager environment, providing declarative transaction demarcation support for multiple SessionFactories. One idea suggested in the forum link is to create the multiple TransactionManager beans in the Application Context XML file, and give them unique names - then add a field to the @Transactional annotation, so we could then reference the TransactionManager by name in the Service method.

For example:

<bean id="txManager1" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
  <property name="sessionFactory">
    <ref local="sessionFactory1" />
  </property>
</bean>

<bean id="txManager2" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
  <property name="sessionFactory">
    <ref local="sessionFactory2" />
  </property>
</bean>

<tx:annotation-driven>
  <transaction-manager ref="txManager1" />
  <transaction-manager ref="txManager2" />
</tx:annotation-driven>

Then, in the application code:

@Transactional(name="txManager1")
public String getFoo()
{
    return dao.find("foo");
}

@Transactional(name="txManager2")
public String getBar()
{
    return dao.find("bar");
}

---

Affects: 2.5.6

Reference URL: http://forum.springsource.org/showthread.php?t=27754

[spring-projects-issues]

Juergen Hoeller commented

This has already been implemented for Spring 3.0 and is available in recent 3.0 RC1 snapshots: using @Transactional value Strings for differentiating among multiple PlatformTransactionManagers. Feel free to give it an early try :-)

Juergen

[spring-projects-issues]

Tom Spencer commented

Brilliant! One step ahead of the game, as always ;-) Thanks very much for the info, just goes to show I should have read the roadmap before posting.