[
https://issues.apache.org/jira/browse/FELIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Wilson updated FELIX-4100:
-------------------------------
Description:
Consider an OSGi runtime with multiple running HttpServices.
Currently it is not possible to control which HttpService the Felix whiteboard
binds to for registering servlets and we get random behaviour. It would be
natural to provide a configuration setting for the whiteboard that allows to
specify a standard OSGi filter.
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).
was:
Consider an OSGi runtime with multiple running HttpServices.
Currently it is not possible to control which HttpService the Felix whiteboard
binds to for registering servlets and we get random behaviour. It would be
natural to provide a configuration setting for the whiteboard that allows to
specify a standard OSGi filter. This filter could then be used when calling
superclass constructors from
{code}
org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker
{code}
It might also be appropriate to integrate the configuration setting with the
standard ConfigurationAdmin service (this may deserve its own JIRA ticket
though).
> 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: Improvement
> Components: HTTP Service
> Affects Versions: http-2.2.0
> Reporter: Mike Wilson
>
> Consider an OSGi runtime with multiple running HttpServices.
> Currently it is not possible to control which HttpService the Felix
> whiteboard binds to for registering servlets and we get random behaviour. It
> would be natural to provide a configuration setting for the whiteboard that
> allows to specify a standard OSGi filter.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
