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=29390>. 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=29390 Improve location independence by not requiring docBase attribute in context.xml Summary: Improve location independence by not requiring docBase attribute in context.xml Product: Tomcat 5 Version: 5.0.25 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently, the Context element in context.xml requires the docBase attribute to be specified. However, the presence of absolute path in context.xml makes sharing of context.xml with other developers impossible. I suggest the docBase attribute is made optional in some situations. Specifically, the following use case is not supported in the current situation: 1. The war file (or expanded war structure) is deployed locally, so it's already present on the machine where I run Tomcat, before deploying. 2. The war file is not under Tomcat's webapps directory; it resides outside the server installation 3. context.xml into placed in the archive's META-INF directory, as recommended by http://jakarta.apache.org/tomcat/tomcat-5.0-doc/appdev/deployment.html 4. I want to share the application sources (including context.xml) with a colleague who keeps the sources in a different location (or uses a different OS). In this scenario, I am currently forced to specify absolute path in the docBase attribute, which makes versioning and sharing of context.xml impossible. I suggest in the case when context.xml resides under META-INF, docBase should not be required. See also issue 27916 for related discussion and for an outline of a solution. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
