Sounds to me like some action chaining could help you out here: SomeUpdateThing.action=BeginTx SomeUpdateThing.success=ActuallyUpdateThing.action ActuallyUpdateThing.action=UpdateThing ActuallyUpdateThing.success=FinishUpdateThing.action ActuallyUpdateThing.error=StopUpdateThing.action FinishUpdateThing.action=CommitTx FinishUpdateThing.success=success.jsp StopUpdateThing.action=RollbackTx StopUpdateThing.success=error.jsp
-Pat ----- Original Message ----- From: "Gavin King" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 08, 2002 3:19 PM Subject: Re: [OS-webwork] Callback after view is rendered > Yeah, I thought of that, but it seems to make exception handling a bit more > difficult. I suppose it need not, if error.jsp also did a callback..... > > More importantly, it doesn't seem to be the responsibility of the view to > ensure that transactions get committed / rolled back. > > ----- Original Message ----- > From: "James Cook" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, November 09, 2002 5:11 AM > Subject: RE: [OS-webwork] Callback after view is rendered > > > > I agree with the filter approach, however an unsophisticated technique > that > > can be applied to just those pages that you are interested in is to embed > a > > callback to your action in the web page. We use this approach to time how > > long it takes for an action to complete, including the client-side > > callbacks. > > > > ... > > </body> > > </html> > > <% someCallback() %> > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:opensymphony-webwork-admin@;lists.sourceforge.net]On Behalf Of > > > Gavin King > > > Sent: Friday, November 08, 2002 7:07 AM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [OS-webwork] Callback after view is rendered > > > > > > > > > > > > > > > > > Hav you tried using a servlet filter for this? > > > > > > > > /Rickard > > > > > > I havn't tried anything at all. I am mainly asking for a > > > recommended "best" > > > approach that I can add to our doco. If thats the best approach, I will > > > write that :) > > > > > > Thanks Rickard. > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by: See the NEW Palm > > > Tungsten T handheld. Power & Color in a compact size! > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > > _______________________________________________ > > > Opensymphony-webwork mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: See the NEW Palm > > Tungsten T handheld. Power & Color in a compact size! > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
