DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27916>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27916 context.xml in war appears to require a docBase ------- Additional Comments From [EMAIL PROTECTED] 2004-05-27 09:39 ------- I may have a different motivation than David, but I too think that docBase should not be required in some situations. Consider the following scenario: 1. I deploy the war file (or expanded war structure) locally, it's already present on the machine where I run Tomcat. 2. The war file is not under webapps; it resides outside the server installation 3. I have put context.xml into the archive's META-INF directory, as recommended by http://jakarta.apache.org/tomcat/tomcat-5.0-doc/appdev/deployment.html In this case, I will supply the location of the war file when deploying using manager, and I expect the server will use the 'path' attribute for the context path. However, it shouldn't require the 'docBase' attribute, as that's already determined by the war location. After all, Jan Luehe says in his evaluation of 28272 that sometimes docBase is ignored: 'path' attribute inside META-INF/context.xml is used, whereas 'docBase' attribute is ignored (it is implicitly set to the WAR file location). Currently, omitting 'docBase' in my scenario will not work, because the server will not find the deployed application after restart. I suggest this could be fixed as follows: When manager deploys the application, then besides copying context.xml into $CATALINA_BASE/conf/Catalina/localhost, it also maintains information about the 'docBase' of deployed applications for apps that do not specify docBase in context.xml. (This could be done by maintaining a properties file that maps file names of context.xml files in $CATALINA_BASE/conf/Catalina/localhost to real docBase locations of the applications.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
