I'd like to offer two cents on this topic. I have seen both very successful
and very unsuccessful results when using servlet reloading on Tomcat. First,
make sure that the servlet classes reside in /webapps/ROOT/WEB-INF/classes.
Next, make sure that the web.xml file in the webapps/ROOT/WEB-INF folder
contains the appropriate entry to register the servlet. Finally, make sure
that the reloadable attribute for the given context is set to "true" in
/conf/server.xml.
Tomcat has demonstrated consistent success in reloading servlets that I
invoke directly from the CLI of my browser, following the above
prescription. If I try to vary this formula (place servlets in other
directories, package servlet classes together, invoke a servlet from another
servlet) servlet reloading seems to get hosed and I end up restarting Tomcat
in order to "see" the new class files.
scott
G:\tomcat\webapps\ROOT\WEB-INF
From: "Benoit Jacquemont" <[EMAIL PROTECTED]>
> This feature exists, it is defined by the reloadable parameter for the
> Context. But it is an alpha version feature, so you always need to restart
> Tomcat.
>
> Benoit
>
> > Hi,
> >
> > Is there any option in tomcat CONFIGURATION by which, I can
> > instruct Tomcat
> > to restart automatically whenever a servlet gets modified (i.e. I
> > re-compile the servlet).
> >
> > I am running Tomcat and Apache on Linux OS.
> >
> > Regards,
> > Marathe
>
