DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26341>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26341 It's possible to call getAttribute() while session is invalidated without IAE Summary: It's possible to call getAttribute() while session is invalidated without IAE Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Servlet & JSP API AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While the session is invalidated all SessionBindingListener are notified with valueUnbound(). In valueUnbound() it's possible to call e.g. getAttribute() on the invalidating session without getting an IllegalArgumentException (which wasn't possible in Tomcat 4.1.29). And according to the servlet-spec (2.3 or 2.4) it shouldn't be possible: Except from HttpSession-API ... For session that are invalidated or expire, notifications are sent after the session has been invalidatd or expired. ... I would interpret this as: The valueUnbound() should be called AFTER the session is invalidated and so I have to get an IAE when calling session.getAttribute() in valueUnbound(). Thanks Lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
