Re: cannot reload servlets

[Paul Downs <pa...@positive-internet.com>]

Hi,
  It is kinda experimental 3.2.x but I have had some success with adding 
reloadable="true" to the relevant context in server.xml.  They say it leads 
to performance degredation although I have no way of benchmarking by how 
much..

Paul

Re: cannot reload servlets

[Paul Downs <pa...@positive-internet.com>]

Hi,

> classes - it checks for changes to the *requested* servlet only.

  Ah damn, thanks for the clarification tho'.

Paul

Re: cannot reload servlets

["Craig R. McClanahan" <cr...@apache.org>]

On Fri, 14 Sep 2001, Paul Downs wrote:

> Date: Fri, 14 Sep 2001 17:26:26 +0100
> From: Paul Downs <pa...@positive-internet.com>
> Reply-To: tomcat-user@jakarta.apache.org,
>      Paul Downs <pa...@positive-internet.com>
> To: tomcat-user@jakarta.apache.org
> 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

Re: cannot reload servlets

[Paul Downs <pa...@positive-internet.com>]

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.

Paul

Re: cannot reload servlets

[Sampath K Settipalli <Sa...@genome.wi.mit.edu>]

Hi,

      I've the same problem and still struggling to get the servlets/classes
reloaded. I'm using Tomcat 3.2.3 on solaris and apache 1.3.20 . I placed my
servlets under /ROOT as per standard directory structure..
webapps/ROOT/sqdev/WEB-INF/classes . sqdev is Application name. I tried even
placing the servlets in /lib . But still it doesn't reload. I had this context
entry in my server.xml

<Context path=""
   docBase="webapps/ROOT/sqdev"
                 debug="9"
                 reloadable="true" >
 </Context>

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.

Can some one please suggest any thing further I can try. I need this badly for
our development environment where we will be making changes frequently. So we
need the reloading.

Thanks in advance,
Sampath


Paul Downs wrote:

> Hi,
>   It is kinda experimental 3.2.x but I have had some success with adding
> reloadable="true" to the relevant context in server.xml.  They say it leads
> to performance degredation although I have no way of benchmarking by how
> much..
>
> Paul