Hello Christoper, > Oh, okay. That makes more sense. :)
Thank you ;-) ! I'm in a very early experimental state concerning this application. There is nothing in the session but a single String (for testing). And you're right, the same sessionid is comming from the client, but tomcat has forgotten which user/principal is associated with the session (which is otherwise in the exact-same state as before the server restart). Currently I'm having a look at the authenticator classes to see what they are doing to register the user with the session. Maybe I can emulate this. And then I would surely need your suggested technique to register a filter to put an object into the session when the user has logged in in the first place. So thanks again for the tip. But I'm still a little perplexed that so much effort is necessary. At the beginning I suspected that this should be part of persistence, too. Did you ever try PersistentManager with Tomcat 4.1 and container based authentication? Did your setup behave differently? Greetings Andreas Mohrig ____________________ - IT-Entwicklung - cadooz AG- Gutschein- und Pramiensysteme Osterbekstr. 90b 22083 Hamburg Email: [EMAIL PROTECTED] Tel.: ++49.40.271 482-13 Fax.: ++49.40.271 482-11 Web: www.cadooz-business.de www.cadooz.de www.directchoice.de www.golfgutschein.de www.valuetracker.de Die cadooz AG ist ein Unternehmen der C1 Group (www.c1-group.de). -----Ursprungliche Nachricht----- Von: Christopher Schultz [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 12. November 2003 18:00 An: Tomcat Users List Betreff: Re: AW: Container based authentication and session persistence with T omca t 4.1.29 Andreas, > Concerning my intentions, I do not want to preserve the session-state > between two logins or between more than one session for a given user. I want > to preserve the session-state between server-restarts in case of necessary > (but normally fast) maintenance operations (changes on certain class-files > etc.). Oh, okay. That makes more sense. :) > What I would need is a way > to manipulate the list the internal table tomcat seems to be keeping of > sessionid->Principal mappings. Then I could use the deserialization of some > object as a hook to place the correct Principal where it really belongs. > Does anyone know how that could be accomplished? I would think that if your session were serialized across a re-start, the session id would not change. In addition, the client (browser) would still send the same session id to the server. It seems like there should not be a problem, here. Perhaps you have other things in your session that are not serializable? -chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
