On 1/10/06, Zach Moazeni <[EMAIL PROTECTED]> wrote:
> I tried both attributes, which worked however the server doesn't detect
> new pages like it used to. (If you update a jsp, it continues using the
> cached version)
>
This is a documented bug according to
http://tomcat.apache.org/tomcat-5.5-doc/
Hello again Zach,
As the documentation notes, antiResourceLocking will prevent JSP reloading
on a running server. If jar locking is your only problem, you should be able
to just use antiJARLocking.
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
-Brian O'Rourke
On 1/9/06, Zach Moaz
I tried both attributes, which worked however the server doesn't detect
new pages like it used to. (If you update a jsp, it continues using the
cached version)
-Zach
Brian O'Rourke wrote:
On 1/5/06, Zach Moazeni <[EMAIL PROTECTED]> wrote:
Hello,
I'm currently on a project using JSF, Sprin
On 1/5/06, Zach Moazeni <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm currently on a project using JSF, Spring and Hibernate deploying to
> Tomcat 5.5.9. I'm also using Eclipse / MyEclipse deploying directly to
> Tomcat. I'm constantly having an issue where Tomcat will keep a hold on
> the jars tha
Hello,
I'm currently on a project using JSF, Spring and Hibernate deploying to
Tomcat 5.5.9. I'm also using Eclipse / MyEclipse deploying directly to
Tomcat. I'm constantly having an issue where Tomcat will keep a hold on
the jars that are in the WEB-INF/lib directory slowing down my developme
