Pax Web serves static resources (#448).

After intense experimentation with different Felix versions (3.2.1, 3.2.2, 4.0.3), that is OSGi 4.2/4.3 specs, Bundle versions (in particular File Install), Pax Web versions (1.x, 2.x, 3.x), and different configurations (in particular File Install's noInitialDelay), there is a minor progress: With Felix 4.0.3 and Pax Web 1.1.3 we can serve static resources!

The 403 Forbidden mentioned before was a result of the different ways Felix HTTP Jetty and Pax Web pass resource names to a org.osgi.service.http.HttpContext.

However the REST services (the Jersey servlet) are *not* functional. So DM is not yet working with Pax Web.

Furthermore I identified a serious bug (related to resouce registration) in Pax Web 3.0.2 that was not there in Pax Web 2.x or Pax Web 1.x. I will inform the Pax Web guys about that.

The overall experience with Pax Web is very frustrating. There are a lot of different versions and no one knows which work together with Felix version on standard bundle versions resp. what are Pax Web bugs. I tried about 100 ;-) combinations and it seems the *only* one that could yield the minor progress mentioned above is Felix 4.0.3 and Pax Web 1.1.3 and setting File Install's noInitialDelay setting to true (plus doing an ugly workaround in the felix.fileinstall.dir configuration). Other Pax Web versions, even other 1.1.x ones, do not work.

Perhaps it is not by accident Danny suggested to use Pax Web 1.1.3 as this is the version deployed by Karaf as well. Other users also report about lot of bugs in Pax Web.

Another field of horror is the Felix File Install bundle, which also exists in a lot of differnt versions, all behaving differnetly. A lot of exceptions are thrown, more or less OSGi internal ones, so the developer has little chance to understand what is going on.

Now I will try to get the REST services working, that is the Jersey servlet (there are a lot of verisions ;-). Frankly spoken, for the moment I don't feel confident to get it running, and for the moment I don't know how much time I should still spend on this frustrating ground. But who knows, perhaps I get little more insights or minor progress that will boost my motivation.

See #448.