hm, i remember that filter also setting the application. maybe i did
not remember correctly. anyways, you can simply write your own filter
then.
-igor
2009/8/30 Uwe Schäfer <u...@thomas-daily.de>:
> Igor Vaynberg schrieb:
>>
>> even though it is session specific it still sets application threadlocal.
>
> does not work, and does not look like it would:
>
> public void doFilter(ServletRequest request, ServletResponse response,
> FilterChain chain)
> throws IOException, ServletException
> {
> HttpServletRequest httpServletRequest = ((HttpServletRequest)request);
> HttpSession httpSession = httpServletRequest.getSession(false);
> if (httpSession != null)
> {
> ... // sorry, dont have one
> }
> else
> {
> log.debug("could not set Wicket session: no http session was created yet
> for {},{}", httpServletRequest.getContextPath(),
> httpServletRequest.getServerName());
> }
>
> try
> {
> // go on with processing
> chain.doFilter(request, response);
> }
> finally
> {
> Session.unset(); // was not set before in this case?
> }
> }
>
>
> what am i missing ?
>
> cu uwe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
