On Thu, May 28, 2009 at 11:24 AM, Johan Compagner wrote:
> why are you using invalidateNow?
>
I was using it for invalidating sessions on logout. But since plain
invalidate() works, and doesn't break RequestLogger, my original problem is
fixed.
Regards,
Taneli Korri
why are you using invalidateNow?
On Thu, May 28, 2009 at 10:11, Taneli Korri wrote:
> On Thu, May 28, 2009 at 6:49 AM, Jeremy Thomerson <
> jer...@wickettraining.com
> > wrote:
>
> > Please open a JIRA so this doesn't get lost. I haven't looked, but it
> > sounds wrong if it truly recreates an
On Thu, May 28, 2009 at 6:49 AM, Jeremy Thomerson wrote:
> Please open a JIRA so this doesn't get lost. I haven't looked, but it
> sounds wrong if it truly recreates an invalidated session in some
> end-of-request logging, even if it doesn't bind the session. Post the
> link back here.
>
>
I f
Please open a JIRA so this doesn't get lost. I haven't looked, but it
sounds wrong if it truly recreates an invalidated session in some
end-of-request logging, even if it doesn't bind the session. Post the
link back here.
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, May 27, 2009
Hi,
I'm using Wicket 1.3.6 and RequestLogger.getLiveSessions to get the current
sessions in my web application, but I'm experience strange behaviour when
session invalidation occurs.
When the user logs out of the application, the session is invalidated. This
leads to WebApplication.sessionDestroy
