I had a similar problem, I wouldn't go so far as to say I have a
solution, but fiddling with the <tomcat>/conf/web.xml file to have the
following in its "jsp" section seemed to help a bit (currently used for
our demo level systems):
<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>false</param-value>
</init-param>
<init-param>
<param-name>reloading</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>checkInterval</param-name>
<param-value>120</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>
Although to be honest I suspect that the best solution for production
boxes is to pre-compile all jsps into the war file anyway.
Mark
On Mon, 2005-08-22 at 14:24 +0200, Michal Kwiatek wrote:
> I've just noticed that on tomcat 5.5.9 JSPs unpacked by tomcat from a
> deployed war file have creation dates pointing to the time when the
> files were first created. On tomcat 5.0.28 unpacked files have creation
> dates pointing to time when they were unpacked (i.e created on this file
> system). Perhaps this is the reason for strange problems with JSP
> recompilation?
________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs SkyScan
service.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
