On Tue, 20 Mar 2001, Ali Ozoren wrote:
> Hi all, I’m new in this list so please be patient. I looked into docs and
> mail archives, and deja but couldn’t find a solution to the problem. Every
> time I make a chance in the formbean, action, jsp, or the strut-config.xml
> file, I have to stop and restart Tomcat. Is this necessary (if yes, dang!),
> if not how can I correct this (making every change not requiring restarting
> Tomcat)?
> Thanks
> --a
>
You should set up a <Context> element in your server.xml file with the
reloadable="true" attribute. Then, Tomcat will reload your application
when any class that is in WEB-INF/classes is changed.
Note that Tomcat 3.2 has some inconsistencies in this regard, and does not
always detect changes to bean classes. Tomcat 4.0 cures this deficiency.
In addition, Struts offers a standard action that tells Struts to reload
its configuration files (see the <Action path="/admin/reload"> entry in
the example application). However, this by itself will not deal with
changed Java classes -- the servlet container has to take care of that for
you.
Craig
