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=13392>. 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=13392 When tag pooling is enabled, release() is not called on tag instances [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-18 02:09 ------- I would think that this is certainly a bug: 1. judging by the number of duplicate bugs reports targeting it. 2. The behaviour is a gotcha for developers. 3. Other major appservers are handling the behaviour as expected. 4. Why should there be any differences in behaviour when tag pooling is turned on or off. Developers should be transparent to it. System Admin perhaps will be more interested, since it is system-tuning related. 5. It is normal to save tag attribute values in tag instance variables. If release() is not called, there is no way to reset them right. I hope no one is going to suggest saving the tag attribute value in the request's attribute, if so where should the code to remove these attributes be? in release()??? Maucherat, if this is a bug for the Jasper, could you just forward it to the person in charge? Or maybe we should clarify this issue with SUN or the tomcat community at large regarding http://jakarta.apache.org/taglibs/guidelines.html thanks. -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
