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=25373>. 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=25373 Timestamp on generated .java and .class should match the one on .jsp ------- Additional Comments From [EMAIL PROTECTED] 2004-03-01 12:22 ------- Nothing in the spec dictates what the timestamps of the compiled class should be. In fact, an implementation could delete the compiled class file after it is loaded into the JVM. The root cause of this "bug" is tomcat compares the create time of the class file to the last modify time of the JSP. Currently, the JSP is recompiled if the JSP's timestamp is newer than the timestamp of the class file. The real fix is to add the the last modify date (of the JSP) as a "constant" in the java generated file. Then the comparison would be done on the embedded timestamp. But this can also have unknown side effects since I'm not a jasper guru. Choosing a different (or alternate) deployment strategy or precompiling the JSP's would fix your problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
