Re: Tomcat 5.5.12: Output unchanged when servlet changes
- From: pit.grinja@xxxxxx
- Date: 27 Nov 2005 09:47:33 -0800
VisionSet schrieb:
> > Is there an internal Tomcat "class caching"
> > mechanism?
> Yes essentially 'The Program' is Tomcat, your webapp is basically a plugin.
> You can set Tomcat to reload contexts automatically at a performance hit -
> useful for testing.
> Basically it scans directories looking for timestamps.
>
> One of the xml files has an 'auto reload contexts' property or something
> like that.
Thanks for the quick response. I checked for the text "reload" in all
xml files in my tomcat directory tree, and didn´t find much useful
hits. I then started playing around with the web.xml file, and it
turned out that simply changing it (insert a space, then delete it)
would make tomcat to reload servlet. Seems hackish, though. Maybe
things will become clearer over time.
BW, Piet
.
- Follow-Ups:
- Re: Tomcat 5.5.12: Output unchanged when servlet changes
- From: VisionSet
- Re: Tomcat 5.5.12: Output unchanged when servlet changes
- References:
- Tomcat 5.5.12: Output unchanged when servlet changes
- From: pit . grinja
- Re: Tomcat 5.5.12: Output unchanged when servlet changes
- From: VisionSet
- Tomcat 5.5.12: Output unchanged when servlet changes
- Prev by Date: Re: Advice on best objects to use
- Next by Date: Re: Tomcat 5.5.12: Output unchanged when servlet changes
- Previous by thread: Re: Tomcat 5.5.12: Output unchanged when servlet changes
- Next by thread: Re: Tomcat 5.5.12: Output unchanged when servlet changes
- Index(es):
Relevant Pages
|