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 2005/10/05 03:05:03 UTC
DO NOT REPLY [Bug 33453] -
Jasper should recompile JSP files whose datestamps change in either direction (not just newer)
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 tom@squeat.com 2005-10-05 03:05 -------
> On access compilation and its friend the development mode - which you are using
> or you would not have this "issue" - should not be used in production
By "access compilation" are you referring to the development="true" mode which causes recompilation
on every access?
We rely on our JSP pages to be compiled when the date changes and the only *reliable* way to do this is
to touch *all* JSP files whenever we change something. I suspect it is because of the problem Jonathon
has pointed out. Unfortunately, this means the webapp is very slow after each deployment. If this
problem won't be fixed, what is the recommended way to avoid recompiling all pages in a production
environment?
--
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org