2016-02-18 13:42 GMT+03:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > Hi guys, > > <Context path="/override" /> in <war>/META-INF/context.xml was used a lot > for tomcat 6/7 and doesn't work anymore since tomcat 8 (didn't check if it > has been backported, can be). > > It is documented but I don't get why this feature has been removed. > typically checking if path is null or not before setting ContextName would > be enough to keep the feature working. > > Do I miss anything?
The "path" attribute is allowed only when Context element is declared in server.xml. In all other cases it is ignored in Tomcat 5.5/6.0/7.0/8.0/9.0 as far as I remember (for the last ~5 years). It does not work in 6/7, contrary to your claim. The main reasons are reducing ambiguity and implementation of (auto)deployment. Note that 1. There are several steps that occur before context.xml is read. 2. Deployment is protected by a lock keyed by web application name or path. Look for "serviced", "isServiced". Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
