[
https://issues.apache.org/jira/browse/FELIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898934#comment-13898934
]
J.W. Janssen commented on FELIX-4100:
-------------------------------------
this is addressed in RFC-189 (HTTP service update), converting this to a
sub-task.
> Allow filter expression for which HttpService the whiteboard binds to
> ---------------------------------------------------------------------
>
> Key: FELIX-4100
> URL: https://issues.apache.org/jira/browse/FELIX-4100
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
> Affects Versions: http-2.2.0
> Reporter: Mike Wilson
>
> Consider an OSGi system running the Felix HTTP whiteboard service and
> multiple HttpServices.
> Currently it is not possible to control which HttpService the Felix
> whiteboard binds to for registering servlets. We get random binding
> behaviour. It would be natural to provide a configuration setting for the
> whiteboard that allows to specify a standard OSGi filter to refer to the
> desired HttpService.
> This filter could then be used when calling superclass constructors from
> org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.
> It might also be appropriate to integrate the configuration setting with the
> standard ConfigurationAdmin service (this may deserve its own JIRA ticket
> though).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
