tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19103] -
Date Tue, 22 Apr 2003 20:17:32 GMT
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=19103>.
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=19103



kin-man.chung@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |Exception thrown attempting
                   |                            |to use session
                   |                            |"removeAttribute()" method
           Severity|Normal                      |
          Component|Jasper                      |Catalina
           Priority|Other                       |
            Summary|Exception thrown attempting |
                   |to use session              |
                   |"removeAttribute()" method  |



------- Additional Comments From kin-man.chung@sun.com  2003-04-22 20:17 -------
Cloning the iterator in o.a.c.util.Enumerator will remove the
ConcurrentModificationException, and will let this example work.  However, it
will also lead to inconsistent states and makes other failures harder to
detect.  For instance, if an attribute that has not yet been seen during the
iteration is removed, then it will still be included in the iteration even
though it was removed.  In other words, we are getting around failfast in
circumstances it was invented for.

I'd have closed this bug as "WONTFIX" were it not for the fact that there is a
real need for cleaning up the attribute list.  It's too bad that there is no
Enumeration.remove() (like the Iterator.remove) that allows the last referenced
item be removed.  Perhaps the correct fix in Tomcat should emulate such behavior
in removeAttribute?  That is, only allow attribute removal if they have been
referenced in the iteration, and throws an exception otherwise.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message