shumbola wrote: > > > > Johan Compagner wrote: >> >> just let your websession implement the httpsessionlistener >> > That was my first try ;) > But HttpSessionListener requires an empty ctor, WebSession ctor with > parameters (Application, Request). > Is it ok to make a default ctor for my session as calling super(null, > null)? > Followup :) For each logged in user there will be one instance of my WebSession, each implementing HttpSessionListener. So every time a session expires, all WebSession instances will get a notification. Is that what I want? If I'm wrong correct me, please. -- View this message in context: http://www.nabble.com/HttpSessionListener-interface-tf3630232.html#a10137119 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
