Howdy, >Please correct me if I am incorrect! It is my understanding that >session attributes are removed prior to a session being destroyed, >right? In other words, if I have the proper listeners installed, and a >session either times out or gets invalidated, I should see the following >events fire off, in this order: > > attributeRemoved() > attributeRemoved() > . > . > . > attributeRemoved() for each attribute in my session > >then finally: > > sessionDestroyed() > >Do I have the picture here? If so, is there anything that might >interfere with this order?
You're right about the order. You need to want to bind your SessionAttributeListener itself as a session attribute as well. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
