Actually, no, it's not executing them again, it's finishing the original execution. The interceptor does whatever it's supposed to do before the execution of the action, it then turns over control to Struts which decides whether there is another interceptor in the chain, or whether it's time to execute the action. When the action is done, the call returns control back to each interceptor in (as you said) reverse order where it can finish it's work. It's the simplest and most effective way of assuring the interceptors can do both pre-processing and post-processing.
(*Chris*) On Sun, Jul 24, 2011 at 9:28 PM, mohan rao <mohanara...@gmail.com> wrote: > suppose, i'm not using timer interceptor and suppose i'm using timer > interceptor then in such a case that interceptor only triggered but it's > executing all interceptor in reverse order once again in post processing. > why? > > -- > View this message in context: > http://struts.1045723.n5.nabble.com/Doubt-on-Struts-2-Architechture-tp4601232p4629574.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 > >
