Hibernate version: 2.1

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

Debug level Hibernate log excerpt:

Are there any problems in using HiLoGenerator with Spring in a web container?
In this document

http://www.hibernate.org/47.html

It says
"The hi/lo identifier generator built into Hibernate does not work with container managed transactions. "

Femi

HiLoGenerator needs a separate JDBC Connection to fetch the "hi" value in a separate transaction. Unfortunately, this won't work in a JTA environment, where the XA-aware DataSource will always return the same JDBC Connection if a transaction is active.

This also applies to Spring-managed transactions when using JtaTransactionManager as backend strategy: You'll work with JTA underneath then, and with XA-aware DataSources fetched from JNDI, so the same restrictions apply.

However, this does not apply to Spring-managed transactions when using HibernateTransactionManager as backend strategy: Hibernate is able to fetch a new JDBC Connection for the HiLoGenerator then, while still participating in (typically declarative) Spring-managed transactions.

So, in short: This limitation only applies to JTA respectively EJB CMT, but not to Spring-managed transactions with HibernateTransactionManager.

Juergen

Thanks much