The transaction interceptor stuff does raise one limitation of the current approach - the rendering of view is always happen within the interceptor. While it is generally ok to keep your session open during view rendering, the same it is not true for transaction which it is much more expensive ( holding lock, rollback segment, etc ). The same could also apply to other expensive resources.
--- Jason Carreira <[EMAIL PROTECTED]> wrote: > Seems like it might be getting a bit TOO pluggable, but it's an > interesting idea... > > > -----Original Message----- > > From: Heng Sin Low [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, July 15, 2003 4:23 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [OS-webwork] WebWork2 Action Chains and Interceptors > > > > > > Seems like this would be possible if the execution of result > > is done by an interceptor too! > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Parasoft > Error proof Web apps, automate testing & more. > Download & eval WebKing and get a free book. > www.parasoft.com/bulletproofapps1 > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
