ould see it work the way you want.
>
>
>
> From: Matthew Hanlon [mailto:[EMAIL PROTECTED]
> Sent: Tue 6/3/2008 6:18 PM
> To: users@wicket.apache.org
> Subject: Re: Wicket Session and non-Wicket Servlet
>
>
>
> >
> > Check o
.
From: Matthew Hanlon [mailto:[EMAIL PROTECTED]
Sent: Tue 6/3/2008 6:18 PM
To: users@wicket.apache.org
Subject: Re: Wicket Session and non-Wicket Servlet
>
> Check out the api for WicketSessionFilter, it will tell you how to make the
> session available for non wicket servlets.
&
>
> Check out the api for WicketSessionFilter, it will tell you how to make the
> session available for non wicket servlets.
>
>
> http://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wicket/protocol/http/servlet/WicketSessionFilter.html
>
Yeah, that's how I had my filter and serv
Check out the api for WicketSessionFilter, it will tell you how to make the
session available for non wicket servlets.
http://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wicket/protocol/http/servlet/WicketSessionFilter.html
On Tue, Jun 3, 2008 at 4:30 PM, Martijn Dashorst <[EMAI
You can't access the Wicket Session from outside a Wicket request
using Session.get(). It is a thread local that is maintained by the
request cycle. If it was possible in 2.0, then that was a bug and most
certainly a security risk.
You should try to look up the Wicket session in the HttpSession of
Okay, I may have this all wrong, and then that's my problem. I have an
application that was developed under the 2.0 branch that I recently migrated
to 1.4. This application uses a servlet to handle requests for Jasper
Reports, and under 2.0 everything worked great. I store the report request
in
