[jira] [Commented] (KARAF-1128) Introduce -Dkaraf.bind.address property

["David Jencks (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176484#comment-13176484 ] 

David Jencks commented on KARAF-1128:
-------------------------------------

This is unrelated to what I was thinking of.  I really object to using system properties for configuration when we have config admin.  I would like to see a proposal on how to share a piece of config data between multiple config admin config ids, which seems to be what you are thinking of. In the future I would appreciate your opening your own issue instead of changing the meaning of mine so dramatically.
                
> Introduce -Dkaraf.bind.address property
> ---------------------------------------
>
>                 Key: KARAF-1128
>                 URL: https://issues.apache.org/jira/browse/KARAF-1128
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-admin, karaf-core, karaf-webcontainer
>            Reporter: David Jencks
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.6, 3.0.0
>
>
> Lets allow people to configure which host the rmi Registry is exposed on.
> Currently, Karaf binds network services (RMI registry, HTTP server, etc) on all IP addresses (0.0.0.0 interface).
> It could be really helpful to have a property to mention the bind address (something like -Dkaraf.bind.address=192.168.1.1 for instance).
> This property should be used by most of the bundle binding network services (Karaf management bundle for the RMI registry/server, HTTP service wia Pax Web, etc).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira