I haven't mentionned it in my first post bug indeed jsp pages are dynamically generated. It's a CMS application we need to host and this CMS app. generate JSP page "on the fly". I understand Remy reason why not precompiling "on the fly" on production mode in general but as said previously by John it is not a option here.
As I'am not a tomcat developer I obviously don't know all implication of a simple patch in tomcat code. I don't know well how to use CVS too, so I haven't time to search how to do to post a patch via CVS. BUT, as I really like (if possible) this bug been fixed I looked into Tomcat code and I've found some lines that may cause this bug, if it can help someone: - impacted classes are mainly "JspServletWrapper", "JspRuntimeContext" and "JspCompilationContext". - when a jsp is removed, a 404 error is send (normal) and a "remove" counter is increased BUT reference to jsp URI is kept in a collection. - with this "remove" counter increased and reference kept, all request to this jsp URI will send a 404 even if this jsp is recreated after. => it is OK if webapp is reloader because previous collection is cleaned. So, may be a solution, quickly tested on my tomcat-5.0.19 : In JspServletWrapper, line 343, remove reference to this jsp URI in collection when sending 404. To do this, add this line before sending reponse: ---- ctxt.getRuntimeContext().removeWrapper(jspUri); ---- Acc�dez au courrier �lectronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34�/mn) ; t�l : 08 92 68 13 50 (0,34�/mn) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
