anonymous wrote : If you are saying that I have to manually close a context in order to flush/commit, I would say that's a very bad design. Sure, while I am in my unit test I have the option of calling context.close(), a longer running process with various wait states does not have that luxury. It has to be handled internally by the engine in these cases.
The context is *always* closed by yourself. In a longer running process, the wait state will return the thread of control to the caller, which means that you can close the context if needed. This is not a bad design. The Hibernate session mechanism works exactly the same way. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181767#4181767 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4181767 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
