Re: Interceptor Execution Tracing

2009-07-02 Thread Stephen Turner
On Thu, 02 Jul 2009 08:37:28 -0400, Paweł Wielgus wrote: Hi Stephen, turn debug on by adding ?profiling=true after any action address in browser and turning devMode. Read more here: http://struts.apache.org/2.1.6/struts2-core/apidocs/com/opensymphony/xwork2/util/profiling/UtilTimerStack.html

Re: Interceptor Execution Tracing

2009-07-02 Thread Paweł Wielgus
Hi Stephen, turn debug on by adding ?profiling=true after any action address in browser and turning devMode. Read more here: http://struts.apache.org/2.1.6/struts2-core/apidocs/com/opensymphony/xwork2/util/profiling/UtilTimerStack.html Best greetings, Paweł Wielgus. 2009/7/2 Stephen Turner : > I

Re: Interceptor execution

2007-05-16 Thread Ray Clough
I'm just mix-and-matching - not using S1 plugin. But the S2 Filter, mapped to "/*" ought to catch all requests, because filters execute before servlets. Therefore I wonder why the LoginInterceptor doesn't get executed on S1-generated requests (ie. those with a *.do url, or even with a *.jsp url)

Re: Interceptor execution

2007-05-16 Thread Laurie Harper
Ray Clough wrote: I've got a large S1 app into which I'm putting S2 features - starting with a How? Are you using S2 with the S1 plugin? Or just putting both versions into one WAR and mix'n'matching? LoginInterceptor, because the S1 security-implementation was NG. The S2 NG? No Good? Nex