Starting with 1.1.0 default war scanner only considers as web bundles the bundles that have a .war extension.
This breaks up existing bundles and is not suited for all situations as you could install bundles from different sources (urls), urls that not mandatory end with a .war.
Also this adds complexity to the build process based on maven bundle plugin.
A reasonable compromise can be the solution described on a related topic on Spring forum: http://forum.springframework.org/showpost.php?p=190987&postcount=12
{quote}
I understand the need to restrict configuration at some point. On the other hand, if the presence of "WEB-INF/web.xml" is not mandatory but still common in WARs, you could implement a two-stage detection logic in the extender:

1. Check for "WEB-INF/web.xml" in a given bundle -> if present, start bundle as WAR
2. If not present, check for naming pattern "*.war" -> if present, start bundle as WAR

As an alternative, you could use a special header in the manifest (similar to or even equivalent with "Web-ContextPath" which is currently supported in Spring-DM). This is not ideal with respect to OSGi standard compliance, however.

This is certainly not a major issue with the given workaround described above.
{quote}