session.invalidate()

[Ankur Jain Kothari]

i ran a program...and then destroyed the session...i think all the attributes associted with the session are also killed when the session is destroyed...unbound is being called for each of the attributes....

is this right? or did i explain it wrong?

[Christophe Verré]

Yes, attributes will be unbound when the session is invalidated.

[Harpreet Singh janda]

But i think that the listener associated with the attributes will not be called in that case.

Correct me if i am wrong.

[Ankur Jain Kothari]

when the session is destroyed...first the HttpSessionBindingListener is called...and then the HttpSessionAttributeListener

[Harpreet Singh janda]

I tried it but HttpSessionAttributeListener was not being called when session was invalid.

I think i have to re verify it.

[Ankur Jain Kothari]

it does get called...i tested it just now

[Christophe Verré]

I'm not sure about HttpSessionAttributeListener, but HttpSessionBindingListener will be notified.

[Ankur Jain Kothari]

how can i be wrong then..i just tried it

[Christophe Verré]

how can i be wrong then..i just tried it

Nobody is saying that you are wrong. However, "The container I'm using does it this way, so it works that way" is not a good argument. Containers sometimes do things unconventional things.

[Harpreet Singh janda]

Can both of you please let us know the containers you are using ?

[Ankur Jain Kothari]

is it because am using tomcat 6? what if tis question comes in the exam?

[Harpreet Singh janda]

Yes, first HttpSessionBindingListener and then HttpSessionAttributeListener is being called.

I have tested it on TomCat 6

[Ankur Jain Kothari]

thank god..thank you

[Harpreet Singh janda]

But we have to test it again on an earlier version of TomCat

[Ankur Jain Kothari]

actually i have read it here that the exam uses tomcat 5..i thought it woudnt matter....but am not changing any risk...switcing to 5.5