There is a FAQ:
http://jakarta.apache.org/tomcat/faq/windows.html#lock
Awesome. The faq indicates that when:
Context ...
antiResourceLocking=false
/Context
the project files are copied to the temp directory and ran from there.
Does Tomcat still pick up changes to
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:
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
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
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
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
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
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
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
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,
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.
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
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
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
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
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
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
17 matches
Mail list logo
