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=33453>. 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=33453 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-07 15:18 ------- Daryl, see comments #35 - #45 and the 4 patch files I posted in the Attachment section. The patch I submitted in March completely fixes this problem in a manner similar to your suggestion. The patch works by storing the timestamp of the .jsp and all its dependent .jsps as member data in the compiled servlet. The isOutDated() method was modified to compare the timestamp of the .jsp against the added timestamps using != instead of >. (In reply to comment #59) > It would be nice to have re-validation maybe that could be implemented using > magic .java file comments in the japser output "// Jasper-JSP-Prerequisite: > foobar/test.jsp 72383828372000" where both the top level source and all included > fragments are listed with their Epoch millis for timestamp. Then the process > would be to recurse the work/org/apache/ tree, reading all the .java and > performing a simple stat() on the source files. This could be done in the > background with live requests taking priority to be checked on first access > after deployment. -- 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]
