Ok, it looks like setting antiResourceLocking="false" solves this problem, which kind of makes sense. Is there a good explanation on the tomcat site or elsewhere for this behavior?
- Dave > -----Original Message----- > From: Durham David R Jr Contr 805 CSPTS/SCE > Sent: Wednesday, December 15, 2004 2:05 PM > To: [EMAIL PROTECTED] > Subject: Reloading JSP's and other resources > > Hi, > > To make changes to my deployed application, I run an Ant script that > compiles classes and copies JSP's, images, CSS, etc. in to my > latest-build directory. As of Tomcat 5.0.18, changes to > JSP's, CSS and > other files were picked up by Tomcat and displayed in my browser. > However, since switching to Tomcat 5.5.4, these changes are not picked > up. > > I have a server.xml configured like so: > > <Context > docBase="E:\projects\build_temp\TIDEII\prototype\latest-build" > path="/tideii" > displayName="TIDE II" > antiResourceLocking="true" > antiJARLocking="true" > reloadable="true" > backgroundProcessorDelay="2" > cachingAllowed="false"> > > </Context> > > > I have the following headers: > > Pragma: No-cache > Cache-Control: no-cache,no-store,max-age=0 > > > I didn't see any bugs that would explain this. Am I configuring > something incorrectly or missing something new in Tomcat 5.5? > > > - Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
