I'll add documentation on how to use Hibernate's StatelessSession API to Spring's documentation: using the StatelessSession API via the native Hibernate SessionFactory, but integrating with Spring's transaction management.
Further potential for explicit support to be explored for Spring 3.0.
+1 Am currently running into this in 2.5.x with JTA issues:
2009-01-02 20:51:32,160 WARN [ bitronix.tm.BitronixTransaction] ( main) Synchronization.beforeCompletion() call failed for org.hibernate.transaction.CacheSynchronization, marking transaction as rollback only
org.hibernate.SessionException: Session is closed!
and unfortunately StatelessSession shares no common interface with Session for dealing with deferred closes (as noted elsewhere).
For anyone who may update this ticket, the following forum entries are all looking for the same thing:
Can't find the documentation that was supposed to be added according to Juergen's comments. Might be me that's unable to locate it though. Would be nice to have a way of managing the StatelessSession in the same way as the Session (closing session automatically etc).
For my current project we needed to use the StatelessSession to achieve better performance. I have build some framework code so we are able to use the StatelessSession together with a (Stateful) HibernateEntityManager and let it join the same transaction. This works more or less the same as how you can mix an EntityManager together with the JdbcTemplate (use the same connection).
Since there are many requests on the web for this kind of behavior I would like to give our solution to the community in the hope you could benefit from it. The [code|#StatelessSessionFactoryBean.java] is attached to this issue and is tested using spring 3.2.0.RELEASE and hibernate 4.1.9.Final.
To use this just add the bean to your existing context configuration:
(!) Please note that this code will only work with the JpaTransactionManager and (of-course) Hibernate as the Jpa implementation. It also doesn't support suspending of transactions (i.e.: PROPAGATION_REQUIRES_NEW, PROPAGATION_NOT_SUPPORTED).