and by the way, interceptors dont get "called again" after action is completed they just havent "ended" when the action is and result is done.
On Tue, Jul 19, 2011 at 10:17 PM, <mmcken...@wernervas.com> wrote: > The struts2 architecture allows for preprocessing and post processing of > requests. > > What if you wanted to record how long it takes for a request to be > processed? > > You could have an interceptor on the top of your request that records the > start time and the same interceptor will record the end time when the > request is on its way out. > > The struts2 in action book has an excellent chapter on interceptors which > I highly recommend reading. > > Hope this helps. > > Mitch > > > > From: mohan rao <mohanara...@gmail.com> > To: user@struts.apache.org > Date: 07/18/2011 09:06 PM > Subject: Doubt on Struts 2 Architechture > > > > Interceptors stack will be triggered before action class is executed and > after the result. Why it's need to execute interceptors stack once again > after result. I used all the interceptors before triggering an action and > what's the purpose of calling these interceptors once again after action > without doing anything. Moreover it will take time to execute all the > interceptors once again. why the sturts2 architecture is designed like > this. > Please through some light on this. Thank you very much. > > -- > View this message in context: > > http://struts.1045723.n5.nabble.com/Doubt-on-Struts-2-Architechture-tp4601232p4601232.html > > Sent from the Struts - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > >
