Yep. In Wicket 1.3 the default session store implementations have #onUnbind which should be called automatically with either an expiry or an explicit invalidation. If you don't extend from the abstract session store class (AbstractHttpSessionStore), you have to implement something yourself.
Eelco On 6/15/07, Ken Leung <[EMAIL PROTECTED]> wrote: > Is there a way to trap the http session expires so that I can do some of my > own house keeping stuff in my application ? > > thx > ------------------------------------------------------------------------- > 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 > > ------------------------------------------------------------------------- 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
