Re: Question: Strange Session Remove Attribute

Peter Rossbach wrote: Hmm, but I can't find a statement that the valueUnbound get an invalid session, when it called after sessionDestoryed. HttpSessionBindingListener === /** * * Notifies the object that it is being unbound * from a session and identifies the session. * * @

Re: Question: Strange Session Remove Attribute

Hmm, but I can't find a statement that the valueUnbound get an invalid session, when it called after sessionDestoryed. HttpSessionBindingListener === /** * * Notifies the object that it is being unbound * from a session and identifies the session. * * @param eventthe

Re: Question: Strange Session Remove Attribute

Peter Rossbach wrote: Hups, the remove session attribute events after session destory is documented at the servlet spec? Any hint welcome Yes, read the javadoc for HttpSessionBindingListener. Rémy - To unsubscribe, e-mail: [EMAIL

Re: Question: Strange Session Remove Attribute

Hups, the remove session attribute events after session destory is documented at the servlet spec? Any hint welcome Peter Remy Maucherat schrieb: Peter Rossbach wrote: Good answer! But why we emit remove session attribute events when sesssion is destroy? I think the session expire is also a clea

Re: Question: Strange Session Remove Attribute

Peter Rossbach wrote: Good answer! But why we emit remove session attribute events when sesssion is destroy? I think the session expire is also a clean up thing and nobody need the remove attribute events. Because the stupid wording which explicitely mandates the nonsense for sessions isn't prese

Re: Question: Strange Session Remove Attribute

Good answer! But why we emit remove session attribute events when sesssion is destroy? I think the session expire is also a clean up thing and nobody need the remove attribute events. Peter Remy Maucherat schrieb: Peter Rossbach wrote: Hey Remy, can you please explain why the remove attribute eve

Re: Question: Strange Session Remove Attribute

Peter Rossbach wrote: Hey Remy, can you please explain why the remove attribute event notification is wrong when context is destroy? Because you're not actually removing them, you're just cleaning up objects. Did you notice you don't get notifications on start, etc ? Rémy -

Re: Question: Strange Session Remove Attribute

Hey Remy, can you please explain why the remove attribute event notification is wrong when context is destroy? Thanks Peter Remy Maucherat schrieb: Peter Rossbach wrote: Hmm, I see the following problem with the current session expire strategie. Today a) Notify session destroy event =

Re: Question: Strange Session Remove Attribute

Peter Rossbach wrote: Hmm, I see the following problem with the current session expire strategie. Today a) Notify session destroy event => All session attributes are active b) Set session as invalid c) Notify session remove attribute event - Hups => Now the listener detect

Re: Question: Strange Session Remove Attribute

Hmm, I see the following problem with the current session expire strategie. Today a) Notify session destroy event => All session attributes are active b) Set session as invalid c) Notify session remove attribute event - Hups => Now the listener detect IllegalStateException

Re: Question: Strange Session Remove Attribute

Bill Barker wrote: Hey I have review the getIdInteral changes. At expire (StandardSession, DeltaSession) we send first the "SessionDestory events" and after this the "Remove Session Attribute" events. Before we send the remove attribute events the session set to invalid. Hmm: Why we do that? I

Re: Question: Strange Session Remove Attribute

- Original Message - From: "Peter Rossbach" <[EMAIL PROTECTED]> To: "Tomcat Developers List" Sent: Sunday, April 03, 2005 5:04 AM Subject: Question: Strange Session Remove Attribute Hey I have review the getIdInteral changes. At expire (StandardSession, Delta

Question: Strange Session Remove Attribute

Hey I have review the getIdInteral changes. At expire (StandardSession, DeltaSession) we send first the "SessionDestory events" and after this the "Remove Session Attribute" events. Before we send the remove attribute events the session set to invalid. Hmm: Why we do that? I have read the spec 2.4