tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33453] - Jasper should recompile JSP files whose datestamps change in either direction (not just newer)
Date Fri, 28 Apr 2006 14:05:28 GMT
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 jleech@virtela.net  2006-04-28 14:05 -------
(In reply to comment #48)
> As I said earlier, I don't think fixing the edge cases is worth adding the
> related complexity. It's very simple. As for JBoss "fixing" it, Tomcat "fixes"
> it too: you simply need to undeploy/redeploy webapps, and/or add some listener
> to clean up the work directory, which is trivial to do. If that's all you want
> to achieve, why did you focus on a complex patch to Jasper ?

The problem isn't isolated to an "edge" case, it affects the standard way apps
are deployed.  Thus the numerous other people who have encountered it.  As for
my patch being "complex" that's just not true. I added 2 fields to the generated
servlet class and updated the isOutDated logic to use them.  It took all of an
hour to code and test.  I can't believe you're asking me why I wanted to fix
something that is broken rather than bandaid it.



-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message