Ok, but I need my wicket session invalidate() method to be called when
httpSession expires.
I had a look at the source (1.2.6) and what I
saw(AbstractHttpSessionStore.class, line 97) is a call
'SessionStore.unbind(String sessionId)' when HttpSession expires. This
method (in the AbstractHttpSessionStore.class) calls
Application.sessionDestroyed
than call empty 'onUnbind(sessionId)' method. So there are no calls to
httpSession.invalidate() method and to
wicketSession.invalidate();
My wicket session overrides invalidate method:
public void invalidate() {
super.invalidate();
close();
}
super is the WebSession class, and its invalidate method is:
public void invalidate()
{
sessionInvalidated = true;
}
So as far as I understand there is no extra call 'httpSession.invalidate()'.
What do you think about this?
--
View this message in context:
http://www.nabble.com/Problem-with-wicket%27s-WebSession-objects.-Memory-leakage--tf3796071.html#a10740481
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
