Multiple requests does not necessarily mean a long-lived transaction. I was thinking of a general case when one may want to use a redirect thus creating a second request.
Basically, I was asking Pat if the book's framework used Hibernate in a way that supports transactions especially in a component-based manner (where each component is not aware that it is part of a larger transaction). Not necessarily XA transactions, although I realize that XA would be necessary if there are two VMs, or two database connections. I would like to generate a DAO that can be used within a servlet framework (using a stand-alone transaction manager), while allowing the same DAO to be deployed behind a session-façade. I thought he may have accomplished this type of abstraction in his book. -----Original Message----- From: Jason Carreira Why would you want to try to keep a transaction open across multiple requests? Multiple database connections can be handled by a JTA transaction manager (XA 2PC)... Multiple VMs would probably also work with JTA, but why would you want/need this? ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
