DO NOT REPLY [Bug 14798] New: - Using jspDestroy for tag pool cleanup

[bu...@apache.org]

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=14798>.
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=14798

Using jspDestroy for tag pool cleanup

           Summary: Using jspDestroy for tag pool cleanup
           Product: Tomcat 4
           Version: 4.1.12
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: brown@corewebprogramming.com


Hi Jakarta Team,

  Looks as if in Tomcat 4.1.x you are using jspDestroy() to do tag 
pool cleanup. This cleanup should probably be placed in a destroy() method.

Basically, my JSP contains the following (I can send you a WAR file with the 
test code if you email me):


<%@ taglib uri="/WEB-INF/tlds/bug-taglib.tld" prefix="test" %>

<!-- Should be perfectly legal. -->
<%! public void jspDestroy() {
      System.out.println("In jspDestroy");
    }
%>    

<test:doLittle />
   
which produces two jspDestroy's in the generated servlet.  The extra  
jspDestroy is:

  public void jspDestroy() {
    _jspx_tagPool_test_doLittle.release();
  }

And of course, with two jspDestroy methods, the code does not compile.

Thanks,
Larry Brown
brown@corewebprogramming.com

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>