And if you use the WicketSessionFilter
always first TEST if the session is there so:
Session session = null
if (Session.exists())
{
session = Session.get()
}
else you will still have the RequestCycle problem...
johan
On 8/31/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
>
> You don't interact with WicketSessionFilter directly. You just set it up,
> providing name of your WicketFilter ad argument. You need to map the
> WicketSessionFilter to same url as your non-wicket filter/servlet and make
> sure that you use a non-wicket filter WicketSessionFilter gets invoked
> first.
>
> Then in your custom filter/servlet you can obtain wicket session using
> just
> Session.get().
>
> -Matej
>
> On 8/31/07, Thomas Singer <[EMAIL PROTECTED]> wrote:
> >
> > What is the preferred way of obtaining a WebSession from a
> > non-Wicket-Filter/Servlet. I've taken a look at WicketSessionFilter, but
> > this one requires a filterName init parameter and seems to expect the
> > session as a HttpSession parameter. But how the WebSession should come
> > into
> > the HttpSession without setting it from the wicket code?
> >
> > Tom
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
