We just started a comparison of Hibernate and OJB. OJB delivers a set of example EJBs in their download which show how to use container-managed transactions.

The Hibernate documentation seems to recommend letting Hibernate manage plain-vanilla txns, wrapped in stateless Session beans. In other words, to not use container managed txns.

How is this possible? When retrieving a Connection from a DataSource in a managed environment, it was my understanding you cannot call Commit. So is Hibernate somehow detecting the app server and letting the app server commit the txn??

Thanks,

Alex

Absolutely incorrect. Now if the EJBs are utilizing CMT, then it is tru that you cannot explicitly commit the transaction. But outside of CMT, you can call commits against the UserTransaction of the TransactionManager managing the Datasource, which is what Hibernate does.


Where is that? I use Hibernate behind a layer of CMT session EJBs and it works great (just simply do not call UserTransaction.commit()).