[
https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882480#action_12882480
]
Felix Meschberger commented on FELIX-2240:
------------------------------------------
>From the mailing list:
If there are multiple services active in the framework, I could imagine it
would
make sense to be able to bind to more than just a (more or less) randomly
selected one.
How about this: There is a configuration option allowing to specify a
service
selection filter (used as the filter argument to the
BundleContext.getServiceReferences(String clazz, String filter) method). If
this property is not set, the console binds to all HTTP Services available.
Otherwise it binds to only the services matching the filter - actually not
binding at all if there is no matching Service.
Looking back at the code, it is probably not very trivial to bind to more than
a single Http Service. But implementing a filter configuration value, which
allows specifying the actual HTTP Service to use is easy.
> Web Console should allow user to select http service to bind to
> ---------------------------------------------------------------
>
> Key: FELIX-2240
> URL: https://issues.apache.org/jira/browse/FELIX-2240
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: webconsole-2.0.6, webconsole-3.0.0, webconsole-3.1.0
> Reporter: Sahoo
>
> Filing this issue per conclusion reached in the dev mailing list. Currently
> web console binds to the first available http service. This is fine when
> there is only one http service in the runtime, but when an environment (like
> GlassFish) supports virtual servers, there is a http service per virtual
> server. In such a case, web console should expose a configuration option to
> select appropriate service. The option can be a filter string.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
