Hi,
- The SessionLookup class does an explicit session.connection().commit(). Is there a particular reason on not too use the Transaction API? I don't know if something like this would be used in a JTA context or such, but it would still be more flexible.
I don't remember why the explicit commit() line is in there. I'd rather not introduce the transaction API into the tags since anything involving transactions is probably getting into complexity that is beyond what the tags are meant for. If there's a clean way to do it though, seems reasonable.
The SessionLookup currently already does transaction management as far as I can see (there is a commit and rollback). Then only required change would be to start the transaction with session.beginTransaction(), store the transaction at the same place the session is currently stored and do a tx.rollback() or tx.commit() where currently a session.connection().commit() or session.connection().rollback() is done.
Michael
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
