You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/01/13 04:06:17 UTC
DO NOT REPLY [Bug 5826] New: -
Jasper not recompiling modified files
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=5826>.
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=5826
Jasper not recompiling modified files
Summary: Jasper not recompiling modified files
Product: Tomcat 4
Version: 4.0.1 Final
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: warjort@hotmail.com
This has been reported on tomcat-user (not by me)
I couldn't see it here.
JSP source files are not recompiled when they change.
org.apache.jasper.compiler.JspCompiler.isOutDated()
uses jspURL.openConnection()getLastModified() to get the change date.
On Sun VMs at least, this always returns 0L for file:// urls.
The following code works on both windows and linux...
if (jspUrl.getProtocol().startsWith("file")
jspRealLastModified = new File(jspUrl.getFile()).lastModified();
else
jspRealLastModified = jspUrl.openConnection().getLastModified();
}
It was changed March 2001, I reported it under the version I have.
Regards,
Adrian
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>