I posted this to:
JBoss Application Server & JBoss Cache
but got no replies. Hence I'm retrying here, hoping for a bit more luck.


I got hibernate (2.1.8) working with JBoss 4.0.2.

But I noticed that in my session facade, I had to set the transaction context as RequiresNew before using the Hibernate session.

This means that the callers transaction context gets suspended.

For long running transactions (say, a business process that calls various methods in the session facade), does this mean that I will not be able to rollback across the whole process in the event of a failure, or a requirement.

Will this change over time so that Hibernate behaves just like a CMP bean?

Cheers
-raj