About session closing in HibernateDaoSupport

[Rod Johnson]

I use Spring tx mgt with the Spring JtaTransactionManager. Under the covers it obtains and uses the JTA UserTransaction. This means that I get a consistent programming model--I can test with local transactions, such as JDBC, Hibernate or JDO transactions. Also, I get the value-added features of Spring's declarative transaction mgt that EJB CMT doesn't offer, such as rollback rules. And I can test my declarative tx mgt in integration tests outside the container, which is a real productivity gain in my experience.

[ndijkstra]

I use Spring tx mgt with the Spring JtaTransactionManager. Under the covers it obtains and uses the JTA UserTransaction

Rod, i see from what you've posted, the benefits of using JtaTransactionManager. Now, what if i want to use Hibernate with HibernateDaoSupport? Is this transaction manager kept in the configuration? What other configurations do i have to consider in order to make things work in a distributed transaction environment as if i where using HibernateTransactionManager?
I don't seem to understand the relation between Hibernate's transaction management and Spring's support for the former O/R mapping tool.

Greetings

[Colin Sampaleanu]

The Hibernate support classes like HibernateTemplate and HibernateDaoSupport are agnostic to whether you are using HibernateTransactionManager or JTATransactionManager. To get the exact same semantics when moving from HibernateTransactionManager to JTATransactionManager, you would want to combine the latter with also using HibernateInterveptor on the tx declarations, otherwise Sessions will be bound on first creation, not at tx creation, but that's about it.