Pax Web 8 and beyond

[Grzegorz Grzybek]

Hello

It's an information e-mail about the review I'm doing for Pax Web 8 (current master branch). The goal is to have working OSGi CMPN R7 implementation of:

 - Http Service specification, chapter 102 (no changes after R6)

 - Http Whiteboard specification, chapter 140 (changed after R6)

What I found is that Pax Web is not handling _contexts_ properly. It uses confusing approach to "shared" context (with potential security vulnerability), duplicates some interfaces, mixes Http Service and Whiteboard APIs, doesn't handle properly properties like:

osgi.http.whiteboard.context.select = (osgi.http.whiteboard.context.name=my-context)

or (allowed by specification):

osgi.http.whiteboard.context.select = (osgi.http.whiteboard.context.name=*)

or even (defined by specification):

osgi.http.whiteboard.context.select = (&(osgi.http.whiteboard.context.name=*)(any.other=value1))

for whiteboard registration.

I'm not going to throw away any legacy code and even I don't want to touch (much) existing interfaces (though they're almost begging to do it ;)). I'm working in similar way to what I did with Pax Logging - review everything, provide integration tests showing specification compliance and consult with you - the community.

JBO - we can always share the working branches. My current work for now mainly consists of:

 - providing javadocs

 - collecting strange and illegal scenarios allowed for now by Pax Web

 - collecting scenarios which should work, but don't work

regards

Grzegorz Grzybek