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=40823>. 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=40823 Summary: Specifying default context w/empty path outside of server.xml Product: Tomcat 5 Version: 5.5.20 Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The documentation (http://tomcat.apache.org/tomcat-5.5- doc/config/context.html) encourages users to define their context's outside of the server.xml file to enable hot-deployments. The documentation also says "If you specify a context path of an empty string (""), you are defining the default web application for this Host, which will process all requests not assigned to other Contexts" Unfortunately, unless the context is defined inside the server.xml file, Tomcat doesn't recognize the empty string path value. The workaround suggested on the user mailing list was: To specify the default app, you must first delete the existing webapps/ROOT directory, then install your app in webapps/ROOT (or webapps/ROOT.war) or put your <Context> element in conf/[engine]/[host]/ROOT.xml. This bug is to request the documentation be updated to include the instructions for specifying the default context when it's defined physically outside of the server.xml file. The dev mailing list indicated this is also how Tomcat 6 works. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
