Hello Nathan,
> I want to allow my partner, who is doing the page design, graphics, and
> JSP to "bounce" Tomcat remotely WITHOUT giving him an account on my
> machine.
>
> I've already written a simple buildServlet that updates the local copy
> of our CVS project and builds it to the context directory
> (webapps/our_project/). I've added the admin/reload.do Action to catch
> config changes. I've set the reloadable='true' in server.xml for the
> Context. Now I need to provide the ability to "bounce" Tomcat, just in
> case it reloads funny.
>
> Does anyone know of a reliable way to do this?
Here's a possible solution that worked with Tomcat 3.1:
If you made major changes in your web app you sometimes have to "restart" the
servlet context. In the Tomcat web administration ( /admin/contextAdmin ) it is
possible to remove a servlet context and to add new servlet contexts. If your
application is the only one that runs on the Tomcat server the easiest way would
be to give your designer a login and he can remove and add your servlet context
again (this has no effect on your server.xml). If there are other applications
on your server, I would suggest to write your on servlet-context-restart-servlet
(should be very easy by looking at the sources from the admin web app of
Tomcat).
Jens
