As I mentioned earlier I'm completely new to osgi/karaf. So my confidence level is not enough to contribute much ;) You said that it's not backed by the OSGi spec.
As I read: http://www.osgi.org/download/osgi-4.2-early-draft3.pdf (RFC 66 - OSGi and Web Applications Page 11 of 19 Draft March 6, 2009) 5.2.1.1 WAR manifest processing An implementation must register a URL handler for processing implementation specific WAR URLs. When a deployer invokes installBundle to install WARs using the URL generated by createWarURL method, the URL handler gets control, and examines the input URL and adds several manifest entries on the fly based deployer specified options. The URL handler uses the following while computing manifest header values: • WAR file manifest entries – developer defaults • Properties supplied by deployer via install URL (e.g., query string) - deployer defaults • Compute based on additional criteria, e.g., other artifacts in the archive. The WAR manifest headers are modified as described below: ... 3. Bundle-SymbolicName: Required If Constants.Bundle_SymbolicName deployer option is specified in the URL, it will be used. All Page within this Box Otherwise, if Bundle-SymbolicName header already exists in the manifest, it will be preserved. ... 7. Web-ContextPath: Optional Specifies the context path of the web application. If WebContainer.Web_ContextPath deployer option is specified, it will be used. Otherwise, if the header exists in the manifest, it will be preserved. Otherwise, if WebContainer.Web_ContextPath deployer default option is specified in the URL, it will be used. Otherwise, a unique context path value is derived in implementation specific ways. Or I totally missed context? Grazvydas
