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=16001>. 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=16001 Tag.release() not invoked [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2003-08-19 02:16 ------- According to the JSP 1.1 Errata published on 5/31/00 (http://java.sun.com/products/jsp/errata_1_1_a_042800.html see under "Issue 14") the behavior exhibited by Jasper (regarding tag pooling) is not in accordance with the specification for JSP 1.1. The errata recognizes the shortcoming of the original spec, which did not provide any mechanism for clearing the tag handler’s state between uses, and it states that tag instances cannot be reused if they don't correspond to actions with the same attributes, unless release() is called between uses. So, the same instance of the handler can be used for <x:foo att1="one" att2="two"/> <x:foo att1="HELLO" att2="BYE"/> but for <x:foo att1="one" att2="two"/> <x:foo att1="HELLO"/> you either have to use different instances, or you have to call release() before second use. I would assume the same applies for JSP 1.2, unless the specification explicitly states otherwise. The errata is there for everyone to see right along side of the original final specification http://java.sun.com/products/jsp/download.html#specs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
