http://issues.apache.org/bugzilla/show_bug.cgi?id=33453
Your problem is likely that jasper compares the date the old .jsp was compiled and the date of the new .jsp, rather than the two .jsp dates. So there are all kinds of ways it gets out of whack, like rolling a file backward in version control, different timezones on development machines and production servers, etc. See the bug report for full explanation and hilarious Remy Maucherat commentary. In that bug report I have posted attachments containing the fix, as well as a drop-in replacement for jasper-compiler.jar which will fix your problem. You can also clear out the work/jboss.web directory which contains the compiled jsps, or touch all the .jsps before building new .wars. Either will force every .jsp to be recompiled when you redeploy. If it works for you, please vote for the bug, post comments etc. so that the Tomcat team will ignore Remy and incorporate the patch in a future release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919177#3919177 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919177 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
