<spec-quote> SRV.15.1.8 HttpSessionActivationListener public interface HttpSessionActivationListener extends java.util.EventListener All Superinterfaces: java.util.EventListener
Objects that are bound to a session may listen to container events notifying them that sessions will be passivated and that session will be activated. A container that migrates session between VMs or persists sessions is required to notify all attributes bound to sessions implementing HttpSessionActivationListener. </spec-quote> HttpSessionActivationListener is the way to achieve what you are trying to do. Mark > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Andreas Schildbach > Sent: Sunday, April 18, 2004 11:45 AM > To: [EMAIL PROTECTED] > Subject: Detecting Sessions already existent at Tomcat Startup? > > Hello everyone, > > when I start up Tomcat and Tomcat activates any sessions from > SESSION.ser, shouldn't sessionDidActivate() in a registered > HttpSessionActivationListener be called? > > Or is this listener reserved only for Session migrations between JVMs? > > In any case, how can I detect a session if it is already > existent at the > startup of Tomcat? > > Regards, > > Andreas > > p.s. to be more precise, I am using Tomcat 5.0.19 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
