osgi-pluginmanager: Add support for OSGi R6 HTTP/Pax Web 6

Description

The osgi-pluginmanager blueprints use a Pax Web 4 class to expose static web resources. Unfortunately, the signature for this class has changed in Pax Web 6 (to support the new OSGi R6 HTTP Whiteboard module). We need to figure out how to make the blueprint work with both versions of the class or bump the version of the pluginmanager and only support Pax Web 6.

Acceptance / Success Criteria

None

blocks

Lucidchart Diagrams

Activity

Show:

Jesse White October 16, 2017 at 1:17 PM

Seth Leger May 22, 2017 at 2:09 PM

There is an easy way to provide compatibility with both versions of Pax Web: just use 'auto-export' on the service beans in the blueprint. Each bean only implements one interface in either version of Pax Web.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 19, 2017 at 11:38 PM
Updated October 16, 2017 at 1:17 PM
Resolved October 16, 2017 at 1:17 PM

Flag notifications