I've traced it to the fact that we're using symbolic links in a link
tree under the WEB-INF/classes directory. Apparently the newer Tomcats
don't like this. (Or maybe the latest JDK?)
--G
On Sat, Oct 12, 2002 at 11:26:57AM -0700, Craig R. McClanahan wrote:
>
>
> On Sat, 12 Oct 2002, Jacob Kjome wrote:
>
> > Date: Sat, 12 Oct 2002 00:36:50 -0500
> > From: Jacob Kjome <[EMAIL PROTECTED]>
> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> > To: Tomcat Users List <[EMAIL PROTECTED]>
> > Subject: Re: Tomcat 4.0.4 won't reload modified classes
> >
> > Keep in mind that the only classes that would be reloadable are
> > servlets. Classes that aren't servlets will be ignored for reloading
> > purposes.
>
> While this was true for Tomcat 3.x, it is not true for Tomcat 4.x.
> Changes to *any* class (servlet or not) will be detected and cause a
> reload, as long as that class has already been loaded by the class loader.
> (If it hasn't been loaded yet, there's no reason to force a restart.)
>
> >
> > I suggest you read up on the Tomcat manager app. It can
> > stop/start/install/uninstall/deploy/undeploy your app without having to
> > restart the whole server.
> >
> > Jake
> >
>
> Craig
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
Guillermo Payet
O C E A N G R O U P
email: [EMAIL PROTECTED]
http://www.oceangroup.com
http://www.localharvest.org
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
