This week's giveaway is in the Beginning Java forum.
We're giving away four copies of Bad Programming Practices 101 (e-book) and have Karl Beecher on-line!
See this thread for details.
Win a copy of Bad Programming Practices 101 (e-book) this week in the Beginning Java forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

SessionDestroyed and valueunbound order  RSS feed

 
Greenhorn
Posts: 22
AngularJS Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

The following is the sequence of things that happen when you invalidate a session:

1. Container calls sessionDestroyed() on all HttpSessionListeners configured in web.xml (in the reverse order they are declared in web.xml). Notice that although the method name is sessionDestroyed, the session is not destroyed yet. It is about to be destroyed. (Note that sessionCreated is called on the listeners in the order they are declared in web.xml)

2. The container destroys the session.

3. The container calls valueUnbound() on all the session attributes that implement HttpSessionBindinglistener interface.




There is getSession() method in HttpSessionEvent Class used to obtain the seesion that caused such a change, and this method is inherited by HttpSessionBindingEvent,
if HttpSeesionBindingLiseners valueUnbound is caled after session is destroyed, what is the result of calling getSession() from there.
 
The human mind is a dangerous plaything. This tiny ad is pretty safe:
Why should you try IntelliJ IDEA ?
https://coderanch.com/wiki/696337/IntelliJ-IDEA
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!