You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/03/01 15:00:06 UTC

[jira] [Updated] (FELIX-4100) Support osgi.http.whiteboard.target whiteboard property

     [ https://issues.apache.org/jira/browse/FELIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated FELIX-4100:
------------------------------------
    Fix Version/s: http.jetty-3.1.0

> Support osgi.http.whiteboard.target whiteboard property
> -------------------------------------------------------
>
>                 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
>            Assignee: Carsten Ziegeler
>             Fix For: http.base-3.0.0, http.jetty-3.1.0
>
>         Attachments: whiteboard_itest.patch
>
>
> 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.3.4#6332)