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=35696>. 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=35696 Summary: Jasper does not call relase method for non pool custom jsp tags Product: Tomcat 5 Version: 5.0.28 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P3 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] First off all this report is not about the stuff discussed in http://issues.apache.org/bugzilla/show_bug.cgi?id=16001. I am not complaining about the relase method not being called between different invocations of a tag. This is correct and spec compliant. As far as I understand the specs the JSP environment must guarantee that release is called at least ONCE during the lifetime of a tag instance. If this tag is pooled this is done in the _jspDestroy method, but if tag pooling is disabled I see no call to release. I was forced to turn off the pooling because the 3rd party who created the application did implement its tags in a NON spec compliant way such that private internal data does not get reseted correctly for subsequent calls of the same tag instance. I just want to be sure that release is also called in this non pooling case. Regards Rüdiger -- 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
