https://bz.apache.org/bugzilla/show_bug.cgi?id=61877
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> --- I'm +1 on this request. We often tell people "don't modify conf/web.xml" or "don't modify conf/context.xml", but we are encouraging people to make "local" copies of those files like CATALINA_BASE/conf/web.xml. (In reply to Mark Thomas from comment #1) > As far as I recall, no configuration files are read from CATALINA_HOME. They > are always read, and only read, from CATALINA_BASE. I don't think making the > default web.xml an exception is a good idea. Counterexamples: if CATALINA_BASE/conf/context.xml is not present, CATALINA_HOME/conf/context.xml will be read instead. Also, CATALINA_HOME/bin/setenv.sh is executed if CATALINA_BASE/bin/setenv.sh does not exist (this may be considered something other than a "configuration file", but I think it helps illustrate the point). There are at least *some* files that Tomcat will fall-back to in CATALINA_HOME if they are not present in CATALINA_BASE. It's "surprising"[1] to find out that a "stock" configuration file -- one users are actively discouraged from editing -- does not enjoy this kind of fall-back semantics. [1] https://en.wikipedia.org/wiki/Principle_of_least_astonishment -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
