Our server is the one generating the class files (we only copy *.jsp files), from a box that is aproximately one second behind the server. So the generated class ought to be 'internally consistent'.
Deleting class files (and generated source) from the work directory seems to help the reloading, but I still don't understand why this is suddenly a requirement. FYI: I modified CATALINA_HOME/conf/web.xml and explicitly set 'reloadable=true' and 'development=true' in the org.apache.jasper.servlet.JSPServlet mapping. (no difference was observed). > -----Original Message----- > From: Ben Souther [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 23, 2003 1:02 PM > To: Tomcat Users List > Subject: Re: JSP not reloading > > > One condition that can cause this is having class files with > a future date. > This can happen if the machine that you copied them from > didn't have it's > clock set properly. > > Since the date on the class files is higher than the JSP > file, jasper won't > recompile it. > > Zap all the class files in your work directory. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
