Hi, Needless to say, it works for me ;) We routinely save/restore sessions with Serializable attributes. (Although you didn't specify what Tomcat release you're using, I'm assuming and using 5.0.27).
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Carey Boldenow [mailto:[EMAIL PROTECTED] >Sent: Monday, August 09, 2004 5:00 PM >To: [EMAIL PROTECTED] >Subject: serialized objects invalidating session > >I have a web application that is storing 2 objects in each user's >session. I recently made each of those objects implement the >Serializable interface. What I now notice is that if I stop and restart >Tomcat (Tomcat 5.0) the sessions are no longer valid and as a result, >the serialized objects are gone. However, if I refactor those the 2 >objects to no longer implement the Serializable interface, then my >sessions are recovered from disk after server stop and start, but of >course, my non-serialized objects are no longer around. Help! BTW, I am >not seeing any errors in the Tomcat logs when I do serialize those >objects. > > > >Regards, > >Carey > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
