Thanks for the reply, Kirk. Calling touch probably would force Tomcat to reload the jsp, but it's not a complete solution. In production environments, Tomcat polls the filesystem for changes, so until the next polling cycle hits, the app would still get a ClassCastException. Additionally, there are performance implications for for continually recompiling in a production environment (the default checkInterval is zero, which results in no runtime checks for modification).
I considered calling touch or making a trivial change to the jsp (like extra whitespace at the end), but I can never completely eliminate the failure window that way, and it's a bit of a kludge anyways. When Context.reload() is called, something in there reloads the jsps. I just need to find that something. -Eric Kirk True wrote: > > Hi Eric, > > If you call touch on the JSP does it update? This used to work on > versions of JRun back in the 90's. > > Just a shot in the dark... > > Kirk > -- View this message in context: http://www.nabble.com/Programmatically-Force-JSP-Reload-tp21715300p21721735.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
