Re: Reloading JSP's and other resources
There are special ant tasks for deployment and undeployment. I guess you should use those and not just put stuff where tomcat should pick them up for you. On Thu, 16 Dec 2004 10:56:22 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > > I am not really an expert but I think it is beter if you modify > > your application at another location and then redeploy it on > > the server. > > > Heh, I think I know what you're saying. Yes, I modify the application > at a different location than deployment. Just for example, code that > I'm working on might go here: > > E:\projects\application\src > > Then an Ant build script would put the compiled/configured stuff here: > > E:\projects\application\latest-build > > Tomcat, for development purposes would be configured to look at code in > the "latest-build" directory. However, if: > > antiResourceLocking="true" > > in the Context (I made an error in my previous message and had this set > to "false"), then changes that are deployed to "latest-build" are not > picked up by Tomcat. Considering that antiResourceLocking, to me, is a > developmental feature (as opposed to production), then changes should be > picked up. Perhaps I should post a feature request? I'm really only > posting here to make sure that I'm not doing something wrong, before > something is sent to dev. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
> May be it's possible to solve your propblem in more convinient way, > as I said I'm not the biggest expert over here. Honestly, my problem is solved. I'm just kind of thought-lingering on this feature a bit. - Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloading JSP's and other resources
Well antiResourceLocking is not default anymore because you mainly have this problem (in other words need to have this feature) under windows platform with it's file locking... The anti resource and anti jar locking features are supposed to be very powerfull and are ment to avoid such platform specific problems but you have to pay a certain price for it... May be it's possible to solve your propblem in more convinient way, as I said I'm not the biggest expert over here. On Thu, 16 Dec 2004 14:44:04 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > > I am not really an expert but I think it is beter if you modify > > your application at another location and then redeploy it on > > the server. > > I guess you're saying that this feature is mainly so that you can > develop out of the same directory that tomcat is using as a docbase ... > > That would basically make the feature useless if it, in fact, does not > pick up changes to that directory.Redeploying, in a Tomcat sense of > the word (restarting a context), does not make much sense. I guess I'm > still confused about the *real* purpose of this feature. > > - Dave > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
> I am not really an expert but I think it is beter if you modify > your application at another location and then redeploy it on > the server. I guess you're saying that this feature is mainly so that you can develop out of the same directory that tomcat is using as a docbase ... That would basically make the feature useless if it, in fact, does not pick up changes to that directory.Redeploying, in a Tomcat sense of the word (restarting a context), does not make much sense. I guess I'm still confused about the *real* purpose of this feature. - Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
> I am not really an expert but I think it is beter if you modify > your application at another location and then redeploy it on > the server. Heh, I think I know what you're saying. Yes, I modify the application at a different location than deployment. Just for example, code that I'm working on might go here: E:\projects\application\src Then an Ant build script would put the compiled/configured stuff here: E:\projects\application\latest-build Tomcat, for development purposes would be configured to look at code in the "latest-build" directory. However, if: antiResourceLocking="true" in the Context (I made an error in my previous message and had this set to "false"), then changes that are deployed to "latest-build" are not picked up by Tomcat. Considering that antiResourceLocking, to me, is a developmental feature (as opposed to production), then changes should be picked up. Perhaps I should post a feature request? I'm really only posting here to make sure that I'm not doing something wrong, before something is sent to dev. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloading JSP's and other resources
I am not really an expert but I think it is beter if you modify your application at another location and then redeploy it on the server. On Thu, 16 Dec 2004 09:16:41 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > > There is a FAQ: > > http://jakarta.apache.org/tomcat/faq/windows.html#lock > > Awesome. The faq indicates that when: > > antiResourceLocking="false"> > > > the project files are copied to the temp directory and ran from there. > Does Tomcat still pick up changes to the original deployment directory > and copy those to temp? So far, it appears the answer is no, but > wouldn't that be the preferred behavior considering this feature seems > mostly developmental in application? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
> There is a FAQ: > http://jakarta.apache.org/tomcat/faq/windows.html#lock Awesome. The faq indicates that when: the project files are copied to the temp directory and ran from there. Does Tomcat still pick up changes to the original deployment directory and copy those to temp? So far, it appears the answer is no, but wouldn't that be the preferred behavior considering this feature seems mostly developmental in application? - Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloading JSP's and other resources
That would be because I saw a post from someone on the mailing lists. Those setings prevent resource locking (such as under windows platform) when you are trying to access file system or resources withing jar files. There is a FAQ: http://jakarta.apache.org/tomcat/faq/windows.html#lock p.s. those settings didn't help me to resolve my problem (when I just import log4j in a JSP). But seem to help most other people. On Wed, 15 Dec 2004 16:50:24 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > > As far as I know you should have only one antiResourceLocking > > or antiJARLocking true but not both. > > Why would that be, and what exactly do those settings mean? I've read > the config docs on the site, but I'm wondering what Tomcat actually > *does* to implement these features. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
> As far as I know you should have only one antiResourceLocking > or antiJARLocking true but not both. Why would that be, and what exactly do those settings mean? I've read the config docs on the site, but I'm wondering what Tomcat actually *does* to implement these features. - Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reloading JSP's and other resources
As far as I know you should have only one antiResourceLocking or antiJARLocking true but not both. On Wed, 15 Dec 2004 14:47:54 -0600, Durham David R Jr Contr 805 CSPTS/SCE <[EMAIL PROTECTED]> wrote: > 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? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading JSP's and other resources
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: > > docBase="E:\projects\build_temp\TIDEII\prototype\latest-build" >path="/tideii" >displayName="TIDE II" >antiResourceLocking="true" >antiJARLocking="true" >reloadable="true" >backgroundProcessorDelay="2" >cachingAllowed="false"> > > > > > 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]
Re: . Reloading JSP's
Just confirming that this is a known bug with the win32 version. I believe using a recent nightly build fixes this problem. Bill Pfeiffer - Original Message - From: "Drinkwater Glen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 11, 2001 8:32 AM Subject: . Reloading JSP's > I am using tomcat 4.0 beta 5 on win NT and the problem is that when i > make a change to a jsp page tomcat doesnt pick it up, i have tried to > refresh the browser, shut down the start up again and nothing happens. > The only thing i can do is resave the JSP as another name, which is > really annoying. Any ideas on the situation?? > > Glen > > > > -- > The Information contained in this E-Mail and any subsequent correspondence > is private and is intended solely for the intended recipient(s). > For those other than the recipient any disclosure, copying, distribution, > or any action taken or omitted to be taken in reliance on such information is > prohibited and may be unlawful.
RE: . Reloading JSP's
Hi,
> -Original Message-
> From: Michael Wentzel [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 5:31 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: . Reloading JSP's
>
>
> > Try response.setHeader("pragma","no-cache") and
> > response.setHeader("cache-control","no-store") at the top of
> > your .jsps,
> > that will/should prevent browsers and proxies from caching.
>
> This would not be a preferred production solution to the problem
> unless it is absolutely necessary since this is going to remove
> caching of static objects, such as images, and would reduce
> performance on the client-side, but it is a option for debugging
> purposes.
>
> ---
> Michael Wentzel
> Software Developer
> Software As We Think - http://www.aswethink.com
It's file-specific. If you use it with a .jsp, ed gifs are still cached
for example. And yes, it is necessary since you wouldn't want your scripts
getting called once a week for a specified client, would you ? ;>
Greetings, deacon Marcus
RE: . Reloading JSP's
> Try response.setHeader("pragma","no-cache") and
> response.setHeader("cache-control","no-store") at the top of
> your .jsps,
> that will/should prevent browsers and proxies from caching.
This would not be a preferred production solution to the problem
unless it is absolutely necessary since this is going to remove
caching of static objects, such as images, and would reduce
performance on the client-side, but it is a option for debugging
purposes.
---
Michael Wentzel
Software Developer
Software As We Think - http://www.aswethink.com
RE: . Reloading JSP's
Hi,
Check if it's really Tomcat's fault. By default html send to browser is
cacheable, so when you reload you get the old one from local cache. Try
response.setHeader("pragma","no-cache") and
response.setHeader("cache-control","no-store") at the top of your .jsps,
that will/should prevent browsers and proxies from caching. Afaik Tomcat
automatically reloads .jsp, reloadable is only for servlets.
Greetings, deacon Marcus
> -Original Message-
> From: Drinkwater Glen [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 2:33 PM
> To: '[EMAIL PROTECTED]'
> Subject: . Reloading JSP's
>
>
> I am using tomcat 4.0 beta 5 on win NT and the problem is that when i
> make a change to a jsp page tomcat doesnt pick it up, i have tried to
> refresh the browser, shut down the start up again and nothing happens.
> The only thing i can do is resave the JSP as another name, which is
> really annoying. Any ideas on the situation??
>
> Glen
>
>
>
> --
> The Information contained in this E-Mail and any subsequent correspondence
> is private and is intended solely for the intended recipient(s).
> For those other than the recipient any disclosure, copying, distribution,
> or any action taken or omitted to be taken in reliance on such
> information is
> prohibited and may be unlawful.
Re: . Reloading JSP's
I think this is a known bug on win32 only. I can't remember where I read about it though, probably this mailing list. Try a nightly build instead. Cheers, Matt - Original Message - From: Michael Wentzel <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 11, 2001 2:25 PM Subject: RE: . Reloading JSP's > > I am using tomcat 4.0 beta 5 on win NT and the problem is that when i > > make a change to a jsp page tomcat doesnt pick it up, i have tried to > > refresh the browser, shut down the start up again and nothing happens. > > The only thing i can do is resave the JSP as another name, which is > > really annoying. Any ideas on the situation?? > > Is your context set to be reloadable? > > > --- > Michael Wentzel > Software Developer > Software As We Think - http://www.aswethink.com >
RE: . Reloading JSP's
> I am using tomcat 4.0 beta 5 on win NT and the problem is that when i > make a change to a jsp page tomcat doesnt pick it up, i have tried to > refresh the browser, shut down the start up again and nothing happens. > The only thing i can do is resave the JSP as another name, which is > really annoying. Any ideas on the situation?? Is your context set to be reloadable? --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
