You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2005/03/15 21:42:00 UTC
DO NOT REPLY [Bug 34024] New: -
Deserialization of sessions on restart/redeploy does not fire HttpSessionBindingListener valueBound events
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=34024>.
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=34024
Summary: Deserialization of sessions on restart/redeploy does not
fire HttpSessionBindingListener valueBound events
Product: Tomcat 5
Version: 5.5.7
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: efenderbosch@neo.rr.com
More of an RFE than a "bug."
As stated in summary, when the saved sessions are deserialized from disk or
other storage, the individual attibutes in the session do not fire a
HttpSessionBindingListener valueBound event. Maybe this could be optional
behavior configurable in the Manager section of the webapp xml.
To reproduce, simply create a Serializable object that implements
javax.servlet.http.HttpSessionBindingListener. Put a System.out.println in the
valueBound method. Vist a page that puts this object in the Session. Redeploy
the app or shutdown/startup tomcat. You will not see a message indicating that
the valueBound event was fired.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org