Johan Compagner wrote:
> > Tomcat 3.1 and 3.2 seem to reliably detect cases where the servlet class
> > you are actually calling has been changed, but they do not always seem
> > to catch the fact that other classes have been changed.
> >
> > Tomcat 4.0 uses a different mechanism that reliably catches *all*
> > changes to classes found in WEB-INF/classes.
>
> But that is not needed.
> It is nice in a development environment but what happens if i update de war file
> Is that detected and is it automaticly being extracted ect ect?
>
For updating a production app, Tomcat 3.x includes an "admin" application and Tomcat
4.0 includes a "manager" application that can be used to shut down the previous
version of a web app, and bring up a new one, without restarting Tomcat. Neither
version of Tomcat currently does this automatically (and there are some JDK problems
that make replacing an existing JAR file harder than it should be).
>
> That is what's needed if you use tomcat for deployment also (in combo with apache)
>
> johan
Craig
