[FELIX-5349] Add ManagedServiceFactory to HTTP service

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: http.base-3.0.12, http.jetty-3.2.4
• Fix Version/s: http.base-3.0.16, http.jetty-3.4.0, http.bridge-3.0.16
• Component/s: HTTP Service
• Assignee: Carsten Ziegeler
• Reporter: Derek Baum
• Created: 15/Sep/16 16:39
• Updated: 20/Sep/16 06:11
• Resolved: 20/Sep/16 05:47

Description

I need to run multiple HTTP services, with different configurations.

I was surprised to find that felix.http.jetty does not provide a ManagedServiceFactory and so were others as indicated in this stack overflow conversation: http://stackoverflow.com/questions/20074211/osgi-http-bundle-bind-to-two-ports

I have experimented with creating a ManagedServiceFactory for the HTTP service myself. It is difficult to do externally to the http.jetty bundle, as it requires access to internal packages.

I have therefore created a small patch to revision 1760954 which adds a ManagedServiceFactory, without changing any of the existing functionality of the ManagedService. This allows multiple http.jetty instances to be configured using WebConsole, fileinstall or other config admin clients.

I have also added a new configuration property: org.apache.felix.http.name,
which is added as a service property to the HTTP runtime instance. This makes it easier to target a specific HTTP whiteboard service than filtering on the port:
HTTP_WHITEBOARD_TARGET + "=(org.apache.felix.http.name=web1)"

I would be grateful if you would consider adding this functionality.