"Craig R. McClanahan" wrote:
>
> On Wed, 12 Sep 2001, Bojan Smojver wrote:
>
> > Date: Wed, 12 Sep 2001 10:40:21 +1000
> > From: Bojan Smojver <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: Tomcat User List <[EMAIL PROTECTED]>
> > Subject: TC4: web.xml and reloading
> >
> > I looked through the source code and in the documentation of the Loader
> > to see if the change of web.xml will cause an application reload in TC4
> > when relaodable is set to true, but I couldn't find anything that would
> > tell me that explicitly.
> >
> > I'm sure this is the case in TC3.3, I was just trying to establish if
> > that was the case in TC4.
> >
>
> When you set an application's <Context> entry to say "reloadable='true'",
> Tomcat starts a background task that watches for changes to *any* class
> that was originally loaded from /WEB-INF/classes or /WEB-INF/lib. If such
> a change is detected, the app will be reloaded. The default checking
> interval is 15 seconds, and can be changed like this:
>
> <Context ... reloadable="true" ...>
> <Loader checkInterval="5"/>
> </Context>
>
> Of course, you can reload any application at any time (whether or not
> you've set reloadable) by using the Manager application.
My question was about web.xml, not the classes and jars (that's
explained in Loader docs). If web.xml changes, TC3.3 will dump the app
and reload because web.xml gets stored in the DependManager (from
memory). Does TC4 behave the same?
Bojan
