>[...] > Make a hibernate session transparently follow the lifetime of an EJB > transaction, across EJB method calls. If I load an entity in FirstEJB, > then call a method on SecondEJB (within the same transaction) which > loads that same entity, it should be serviced from the same session > cache (assuming FirstEJB and SecondEJB are local to each other, of > course).
Have you try JCA? > In the same vein, flushing and closing the session should occur > automatically at the end of the transaction. Partially I agree. I think that flushing should occur automatically, especially if container manages transactions. But closing is a different story. Closing is simply beyond transaction scope. In the same spirit - you don't bother in how JDBC connections are closed if container manages them.You just want to make sure that transactions are properly demarcated. -- Mike ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
