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=41746>. 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=41746 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-03 06:30 ------- > 1. define the <Context" in server.xml This (need to define context in server.xml when trying to deploy application as default one) isn't mentioned in your documentation describing the use of path attribute (http://tomcat.apache.org/tomcat-6.0-doc/config/context.html), so this could be a documentation bug. >2. rename your app to ROOT Consider the case when you want to change the root app - there is a loot of work you need to do. This is more of a kludge then solution. >3. define a TCHOME/conf/Catalina/localhost/ROOT.xml with a docbase pointing to >your webapp I like this solution, but I don't know how will this work with my "base" context.xml located in META-INF folder. If I add a ROOT.xml = <Context path="" docBase="/lootist"/> will this affect settings in context.xml(persistent manager, logging, JNDI resources availability) ? I think you should consider the case when user doesn't have access to server.xml or the directory where context files are kept. Most of the companies we work for have big concerns about security, and they allows us only the minimum access to there servers and tomcat directories. Proposal: When new app is deployed, and if path="" element is found, Tomcat could create ROOT.xml pointing to the docBase of previously mentioned app. If ROOT.xml already exists, exception could be thrown. -- 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]
