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-06 23:51 ------- I think this is a significant problem when you really have different organizations building and deploying, e.g., for publicly distributed applications. A common timeline would be: January - release 1.0 of app March - JSP in app is updated April - release 1.1 of app frozen for QA May - user downloads and installs 1.0 June - user downloads and installs 1.1 In this case, Jasper will view the compiled date of the 1.0 JSP as May and view it as newer than the change date of the 1.1 JSP. I gather that the "best practice" for building a web app for use with Tomcat would be to touch all the JSP's in your web app in your release process so you minimize the risk (although if someone downloads 1.0 after you released 1.1 they can expect a lot of 500 errors from NoSuchMethodError) I believe Jasper really should remove cached JSP's from the work directory when an app is undeployed (or redeployed). I think this is common, important, and quite different than the rather obscure case of rolling back an older version from version control. This would also avoid a performance hit in checking out of date on JSP's and wouldn't surprise people (I wouldn't expect JSP's to be cached after redeploying an app, indeed I think it's surprising behavior!) One of the users of our Web app just hit this issue today: http://www.glassbox.com/forum/forum/addpost?parent=235 and with a little googling you can see others e.g., http://mail-archives.apache.org/mod_mbox/tomcat-users/200512.mbox/[EMAIL PROTECTED] -- 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]
