DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=18479>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=18479 HttpSessionBindingListener.valueUnbound() not called ------- Additional Comments From [EMAIL PROTECTED] 2004-04-12 01:06 ------- Hi Remy, I have to admit, it looks pretty rock solid, but how is it that in 5.0.20 my session serialized/deserialized *without* error and gave me a non-null attribute value (exactly as I expected) after reload? Serialization is pretty straight forward; either it is serializable and you get no errors or it isn't serializable and you get errors. I get no errors. How is that not the definition of "perfectly serializable"? And if removeAttribute() is being called, why isn't the attributeRemoved() method in my SessionBindingListener being triggered? I have println() statements in all methods of my SessionBindingListener and the only ones I'm seeing are on attributeAdded(). You can go ahead and stick to your guns and say that my object is not serializable (I'm 99.9999% sure it is), but you can't, at the same time, claim that it is being removed from the session when attributeRemoved() is not being triggered.... unless there is a bug where the removeAttribute(keys[i]) call is not notifying listeners of the attributes it is removing. So, I guess I'll have to investigate some more, but something is wrong here. Hopefully we can work together to figure it out. Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
