valueUnbound() event in HttpSessionBindingListener

2002-03-05 Thread Matt Veitas

Doing some digging into the Tomcat 4.0.x source code, I noticed that
valueUnbound is called even on a session's setAttribute method. I would
think that the valueUnbound method would only be called when removing
something from the session. Turns out that when i modify the object that is
stored in the session, the valueUnbound method is called...is modifying an
object really considered to be removing it and then adding it?

Any help with this topic would be appreciated.

Matt


 == mailto:[EMAIL PROTECTED]

Matt Veitas   _/_/_/_/_/_/  _/_/_/
Software Developer   _/ _/_/_/
Object Sciences Corporation _/ _/_/_/
6600 Comet Circle, Suite 512   _/ _/  _/_/_/  _/
Springfield, VA 22150 _/ _/_/_/
voice:   +   _/ _/_/_/
fax: +_/_/_/_/_/_/_/_/_/
 http://www.objectsciences.com/ 


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




sessionClosing event???

2002-01-21 Thread Matt Veitas

I was looking through the code in StandardSession regarding removing an
attribute from the session. I was puzzled that the attributes were removed
and the event fired off...is there a reason for this?

What I am trying to do is to do some cleanup work on the object that was
bound to the session (doing some database stuff). Since the attributes in
the session are removed before the valueUnbound or sessionDestroyed events
are called, I can't do my clean up. Is there any way around this without
going in and changing the code?

I would like to propose additional an additional method such as a
sessionClosing() method so you can do some cleanup before it actually is
invalidated. What do people this about this?


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]