On 7/29/05, Varley, Roger <[EMAIL PROTECTED]> wrote: > > > > I could be losing my mind, but, I swear that I tried this technique > > once and by the time the sessionDestroyed() method was called, I was > > not able to get any of the session attributes back anymore. For > > various reasons, the webapps I develop need to be deployable in a > > Servlet 2.3 environment. Is this something where the behavior changed > > for the better in Servlet 2.4 versus 2.3? > > > > </Lurk> > No, you are not loosing your mind. The Servlet 2.3 specification defines > HttpSessionListener#SessionDestroyed as "Notification that a session was > invalidated". Thus anyone who followed the specification to the letter, as > many container authors did, ended up with a method that was somewhat less > than useful. In the 2.4 specification, the wording was changed to > "Notification that a session is about to be invalidated". >
One approach to consider is to make your listener implement HttpSessionAttributeListener as well as HttpSessionListener. That means you'll hear about session attributes being removed -- which is what happens as the session is being invalidated or timed out. All of these calls will happen before the sessionDestroyed() notification. Craig > I now return you to your regular programmes. > > <Lurk> > > Regards > Roger > > > __________________________________________________________________________ > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. > As its integrity cannot be secured on the Internet, the Atos Origin group > liability cannot be triggered for the message content. Although the > sender endeavours to maintain a computer virus-free network, the sender > does not warrant that this transmission is virus-free and will not be > liable for any damages resulting from any virus transmitted. > __________________________________________________________________________ > > --------------------------------------------------------------------- > 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]
