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=18069>. 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=18069 Changing enablePooling should force page recompiling Summary: Changing enablePooling should force page recompiling Product: Tomcat 4 Version: 4.1.18 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I recently found out that the tag library I was working with was not spec-compliant and was having problems because of tag pooling. So, in an effort to get things working I disabled tag pooling to make sure that was the problem. It was only later that I realized that since I hadn't re-deployed the JSP's, it was probably still using the old work/*/.java files. Deleting everything in the work directory fixed this and now the tags are frolicking again. Since enablePooling is something that affects how the .java files are generated, it seems to me that if Tomcat realizes that the enablePooling setting has changed, that it should force a recompile of all the jsp's the next time they're hit (or whenever). I don't know if this opens up a can of worms (for instance, should it do the same thing if the classdebuginfo setting changes too). But that's why I'm listing the severity as enhancement instead of bug. Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
