DO NOT REPLY [Bug 11815] - ServiceLifecycle.destroy() never called when session is destroyed

[bu...@apache.org]

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=11815>.
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=11815





------- Additional Comments From asfbugzilla@nps.phoenix-int.com  2005-11-03 21:11 -------
This bug does not appear to be fixed for HTTP style sessions.  There are 2
problems that I have found so far:

1) The AxisHTTPSessionListener.sessionDestroyed() event loops on the names of
the session variables looking for ServiceLifecycle objects.  The names are
always strings.  This code should work better:

        Enumeration e = session.getAttributeNames();
        while (e.hasMoreElements()) {
            String nextName = (String)e.nextElement();
            Object next = session.getAttribute(nextName);
            if (next instanceof ServiceLifecycle) {
                ((ServiceLifecycle)next).destroy();
            }
        }

2) For some reason on my box the HttpSession object that gets passed to the
sessionDestroyed event is a _different_ object with a different ID and all the
session properties except the axis.isAxisSession one missing.  This appears to
be a problem in Tomcat, although I'm afraid I really don't understand this one yet.

-- 
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.