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=25738>. 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=25738 org.apache.jasper.JspC has no command switch to disable tag pooling Summary: org.apache.jasper.JspC has no command switch to disable tag pooling Product: Tomcat 4 Version: 4.1.27 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Our development team recently upgraded from tomcat 4.0.6 to 4.1.27 which has tag pooling enabled by default. We all agree tag pooling is a good thing, however we had several jsps which would break when tag pooling is enabled. We've solved the problem by disabled tag pooling under $CATALINA_HOME/config/web.xml. Our longer term plan is to fix all our jsps, but in the meantime we have to work around this. Unfortunately we had been using the "jspc" Ant task to precompile our .jsp files to improve initial access time in production environments. I've read all the warnings and understand the reasoning against this, but our traffic is just too high to avoid it. As a result of using the JspC command to precompile .jsps, I've found there is no way to disable tag pooling from a command line argument. in the JspC.java class there's even a public method: public boolean isPoolingEnabled() { return true; } Is that just a to-do item, or is there some significant reason that can't be set by a main() argument? If this is just something that's yet to be done, I'll happily make the change myself. In any case, jasper's getting a lot of testing in our shop. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
