We're having some issues with JSP files not being recompiled when they
should be, and was wondering if anyone can shed some light on it.
We have Jasper set up in development mode, with the following in
conf/web.xml:
<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>development</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>modificationTestInterval</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>reloadable</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>
</servlet>
The JSP files are being created and updated by a content management
system on a remote box, and then pushed onto the webserver using Rsync.
Tomcat does not always seem to spot that a file has been updated though,
and continues to serve the old jsp. I can force a recompile by
"touch"ing the jsp file, but have no idea why this works, as the rsync
is updating the timestamps whenever the page is updated anyway.
Any advice would be welcome, it's driving our developers a little mad
and me with it.
Dave
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
