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?
> -----Original Message----- > From: James Cook [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 12:56 PM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] hibernate/webwork2 best practices > > > Does the book document the "Yet Another Petstore" as a > web-tier only, or as a web-tier with an EJB (SLSB) backend? > > Does the framework also support an ACID transaction across > multiple requests, against more than one database connection, > or across more than one VM. > > I'll be first in line to buy the book if it does! > > ------------------------------------------------------- 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
