On Mon, Nov 28, 2011 at 4:31 AM, James Carman <ja...@carmanconsulting.com> wrote: > Or use a request cycle listener to be more portable.
request cycle listeners are available since Wicket 1.5 looking at the stacktrace (s)he still uses 1.4 > On Nov 27, 2011 9:22 PM, "Jeremy Thomerson" <jer...@wickettraining.com> > wrote: > >> On Sun, Nov 27, 2011 at 9:14 PM, nazeem <md.naz...@gmail.com> wrote: >> >> > In the server side, i need to know who is performing this action to do >> > auditing and other related services. So I need to use a thread local >> > variable that will be available at any place in the chain of request >> until >> > response is sent back. But I do not know how to set this thread local >> > variable at the time of request. I have the current user in session, so i >> > need to get it from session and set it to thread local variable on each >> > request. if possible distinguish and filter only user request actions >> > instead for all css, js request. >> > >> > When i look at the stack trace, when i click a submit link to update >> > employee.. this is the strucutre. >> > >> > I am interested to intercept between this to set the thread local >> variable. >> > how do i do it ? >> > >> >> >> You can override newRequestCycle in your application, provide a custom >> subclass of WebRequestCycle, and use onBeginRequest / onEndRequest. >> >> -- >> Jeremy Thomerson >> http://wickettraining.com >> *Need a CMS for Wicket? Use Brix! http://brixcms.org* >> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org