Some of the HTTP Service implementations (such as Pax Web) let you specify the context of a deployed webapp by specifying a Webapp-Context: header in MANIFEST.MF.

The Spring-DM Web Extender does not honor this and instead leans on DefaultContextPathStrategy to figure out how to name the context, starting with the bundle's location.

Unfortunately, the location is not necessarily ideal for a handful of reasons, not the least of which is that it is not necessarily going to be the same location everytime I deploy the web bundle. I'd prefer to have some repeatable way to deploy a WAR file, regardless of location, and count on the context path to be the same.

Therefore, I propose that DefaultContextPathStrategy *FIRST* look for a Webapp-Contxt: header in the MANIFEST.MF and, if it finds it, uses its value as the context path. If not, then it should fall back on the existing strategry.