Hi Torrey,
I can't comment on .war file deployment directly because I am not
using it. But I want to help you anyway, suggesting the approach I
would take.
I would forget manager for a moment. A basic servlet engine (these
things have been around for 10 years or more, remember Sun's Java
Server) are capable to reload servlets if any of the watched resources
change.
Server restart for your purpose is a very sad state of affairs, not
acceptable by today's standards.
So I would try to touch any of the watched resources, e.g. a servlet
class file, a servlet jar file or the web.xml file.
That, from my experience with old mod_jserv, does not immediately
trigger class re-loading. Only the next servlet request provides the
event for that (noticable delay of servlet response).
If that does not work, then you have the most basic problem. If it
works, then you have a feeling for how it should work. Then work your
way up to war file deplayment with manager.
I would think that you don't need manager for most management tasks
e.g. war file deployment because who can assume that you want to
introduce a security risk by providing such powerful access to your
application via http???
Playing around a little is sometimes very useful.
Regards,
Bernard
Post by Torrey RiceI have a similar problem in 5.5 when deploying my .war files. If I go to
the manager and undeploy a webapp that was deployed from a war it only
deletes the .war file and not the exploded directory. If I want to
deploy an update I have to stop tomcat and start it again for it to
pickup the change in the war file. Even when I have auto-deploy set to
true.
I have done everything I can think of but it seems that to make an
update like this in Tomcat you have to stop and restart which is really
unfortunate.
Post by BernardRoland,
Normal startup causes server error 500
http://issues.apache.org/bugzilla/show_bug.cgi?id=34050
It might be in the area of your interest.
Regards,
Bernard
Post by Lionel FarbosHi,
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html
I don't know your tomcat version, but it works since TC 4.
Cheers.
On Thu, 17 Mar 2005 08:32:54 +0100
Post by Roland CarlssonHi!
I have a problem with an webapp with deploying webapps. The problem is the
contextfile that since my development environment differs a little to my
deployment environment have to be edited a little after deployment. But how
do I force tomcat to re-load the context? Right now the only way I know
about is to reboot tomcat witch leads to a full stop of all my web-apps
instead of only one witch in turn leads to more complaints from my users.
So, is there a way to force reload of the context when reloading the
web-app?
Thanks in advance
Roland Carlsson
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------