Pax Web 3.0.2 seems to have a bug that is not there in Pax Web 1.x or 2.x:
Resources are only served if there is a servlet registered with the same HttpContext. Otherwise requesting a resource results in 404.
That is resources are not served at all if no servlet is registered.
This seems to be a bug and should be fixed.
Pax Web 1.1.14 / Pax Web 2.1.4:
Registering resources is completely independent from registering servlets.
Resources are served if no servlet is registered.
Resources are served if a servlet with a different HttpContext is registered.
This seems to be correct OSGi behavior (according to API specification).
(Felix HTTP Jetty shows this behavior as well.)
Pax Web 3.0.2
Felix ConfigAdmin 1.6
Pax Runner 1.8.5
Maven Pax Plugin 1.4