DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4829>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4829 Automatic deployment of war files does not work properly ------- Additional Comments From [EMAIL PROTECTED] 2002-02-16 03:21 ------- [Note that this is still the behaviour in 4.0.2]. I must concur with the reporter. The documentation at tomcat- docs/config/host.html leads one to believe that the auto-deployment of the application is orthogonal to the automatic creation of the <context> if it is not supplied. A work-around we have experimented with is to choose a path that is different from the docBase (given that documents.war is in the webapps directory): <Context path=”/docs” docBase=”documents”/> At first this seems to work but there are two problems 1. This actually deploys as two applications, each using the same docBase. Once at /docs and the other at /documents. 2. There is a race condition. If the “/doc” context is started before the documents.war is deployed it will not be found until tomcat is restarted. It does not seem unreasonable to want to have a war file auto deploy and specify a <context> in the server.xml file. I may have an application for which I wish to create files in the applications docBase and want to add parameters to the <context> (e.g. <realm>. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
