Hi All -
I'm using hibernate 2.1 and Spring M3, I think this question boils down to hibernate only:

To use JTA transactions, I would like my hibernate session to participate when a transaction *already exists*, and otherwise, create a JDBC transaction.

I don't see a way to do this, or that it is considered in the code - you can configure *either* JTA, JDBC or none transaction manager - correct?

The problem I have is when a JTA transaction exists, if the hibernate transaction is committed, then when the container commits the JTA transaction, it throws an exception, since it is already commited.

Is the only way to set this up to create my own net.sf.hibernate.transaction.TransactionFactory and net.sf.hibernate.transaction.Transaction that:
- check for a current JTA transaction
- if found, use that transaction, and do not commit it
- if NOT found, create a JDBC transaction, and DO commit it

does this make sense? Is there some better way to approach this? The only other alternative I can think of is to move this logic to my application code and only init the hibernate transaction when a JTA transaction exists, and do not commit it. It seems like this could be a potential problem, though...

any feedback is appreciated

thanks!
Tyson

Tyson,

Please lets keep this discussion in http://forum.hibernate.org/viewtopic.php?t=926452. I don't know where to answer else ;-)

I've just indicated there that Hibernate's JTATransaction (and thus Spring's HibernateTransactionManager) already implements the pattern you propose: Participate in an existing JTA transaction, create a new one else.

The problem is that in the latter case, Hibernate tries to check the SQL warnings via Connection.getWarnings: Unfortunately, WebLogic's JTA is so restrictive that it doesn't even allowing for getWarnings after a transaction commit!

Juergen