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=16031>. 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=16031 Custom tag pools does not reset its handler state when returned to pool. Summary: Custom tag pools does not reset its handler state when returned to pool. Product: Tomcat 4 Version: 4.1.18 Platform: All OS/Version: All Status: NEW Severity: Critical Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Custom tag pools does not reinitalize its handler state when it is returned to the pool. That is, we associate a value with a key for a custom tag. The problem comes the next time the tag is reused, the associated value and its key still remains on the handler tag, and thus the previous status is reused. We think that when the tag work is finished and tomcat returns it to the custom tag pool, it should be done a reset. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
