At 09:22 AM 12/09/01, you wrote:
>Jim Cheesman wrote:
>
> > I have to back this statement up - jar reloading on TC4/Win2000 is a risky
> > business, to say the least. Sometimes it works, sometimes not... I wonder
> > if it's anything to do with the server checking for a new jar at the same
> > tim
Jim Cheesman wrote:
> I have to back this statement up - jar reloading on TC4/Win2000 is a risky
> business, to say the least. Sometimes it works, sometimes not... I wonder
> if it's anything to do with the server checking for a new jar at the same
> time as the filesystem overwrites the old one?
At 05:54 AM 12/09/01, you wrote:
>Remy Maucherat wrote:
>
> > Essentially, yes.
> >
> > JAR reloading is not very reliable on my Windows box, though (and you can't
> > remove JARs; but strangely you can ovewrite them). Sometimes, the changes
> > get picked up, sometimes they do not. I have yet to
Remy Maucherat wrote:
> Essentially, yes.
>
> JAR reloading is not very reliable on my Windows box, though (and you can't
> remove JARs; but strangely you can ovewrite them). Sometimes, the changes
> get picked up, sometimes they do not. I have yet to find the reasons for
> this, unfortunately :
> "Craig R. McClanahan" wrote:
>
> > When you set an application's 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
"Craig R. McClanahan" wrote:
> When you set an application's 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.
Remy Maucherat wrote:
>
> > Remy Maucherat wrote:
> > >
> > > > 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).
> Remy Maucherat wrote:
> >
> > > 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?
> >
> > No
Remy Maucherat wrote:
>
> > 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?
>
> No web.xml reloa
> 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?
No web.xml reloading in TC 4.
Remy
"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
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 documentatio
12 matches
Mail list logo
