On Fri, 14 Sep 2001, Paul Downs wrote:
> Date: Fri, 14 Sep 2001 17:26:26 +0100
> From: Paul Downs <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED],
> Paul Downs <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: cannot reload servlets
>
> Hi,
>
> > Can we do something in web.xml for each servlet entry to make it
> > reloadable ? Is there a way to check the options set (like is the
> > reloadable = 'true' ?) once server is started and running the application
> > for any particular contextpath.
>
> I think a servlet explicitly named in web.xml will get reloaded. The
> only thing is most people seem to have a lot of interdependencies and I am
> not sure how far "down" the tree this works... The person I did it for
> earlier hasn't complained..... yet.
>
Naming or not has *nothing* to do with reloading -- the important
consideration is where the class is loaded from. Only classes under
/WEB-INF/classes and /WEB-INF/lib can be reloaded at all. In addition,
Tomcat 3.2 is not particularly good at detecting changes in non-servlet
classes - it checks for changes to the *requested* servlet only.
> Paul
>
Craig
