You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Sahoo (JIRA)" <ji...@apache.org> on 2010/03/30 16:37:27 UTC

[jira] Created: (FELIX-2240) Web Console should allow user to select http service to bind to

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: shell-1.4.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.


[jira] Commented: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Sahoo (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882688#action_12882688 ] 

Sahoo commented on FELIX-2240:
------------------------------

I tried a build from trunk that has the above fix and it works. Thank you very much.

> 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.


[jira] Commented: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated FELIX-2240:
-------------------------------------

    Affects Version/s: webconsole-3.1.0
                       webconsole-3.0.0
                       webconsole-2.0.6
                           (was: shell-1.4.0)

Fix affected versions

> 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.


[jira] Commented: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882481#action_12882481 ] 

Felix Meschberger commented on FELIX-2240:
------------------------------------------

In Rev. 957829. implemented support to specify a selection filter for the HTTP Service to which the Web Console should bind.
If the filter is empty or not set (the default), the Web Console binds to any HTTP Service provided by the framework.

Would that suit your need ?

> 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.


[jira] Closed: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed FELIX-2240.
------------------------------------


Apache Felix Web Console 3.1.2 has been released. The issues are now closed.

> 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
>            Assignee: Felix Meschberger
>             Fix For: webconsole-3.1.2
>
>
> 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.


[jira] Resolved: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved FELIX-2240.
--------------------------------------

         Assignee: Felix Meschberger
    Fix Version/s: webconsole-3.1.2
       Resolution: Fixed

This can be resolved because it has been confirmed working.

> 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
>            Assignee: Felix Meschberger
>             Fix For: webconsole-3.1.2
>
>
> 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.


[jira] Commented: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882471#action_12882471 ] 

Felix Meschberger commented on FELIX-2240:
------------------------------------------

Here is the mail thread: http://markmail.org/message/q5r22pyq4rs6r3v4

> 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.


[jira] Commented: (FELIX-2240) Web Console should allow user to select http service to bind to

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882502#action_12882502 ] 

Felix Meschberger commented on FELIX-2240:
------------------------------------------

Had to move initial configuration of the console to after loading the initial plugins in Rev. 957858.

This is required since the HTTP Service is now started to be tracked when the console is configured. This may cause a race condition between the Http Service being bound and built-in plugins being registered but not initialized.

> 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.