[
https://issues.apache.org/jira/browse/KARAF-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468750#comment-13468750
]
Matthew George edited comment on KARAF-581 at 10/4/12 6:13 AM:
---------------------------------------------------------------
I should also mention that the same issue exists for the rmiServer, there needs
to be an option for rmiServerHost and rmiRegistryHost, not just rmiRegistryHost
to allow explicit binding to a specified interface for all listeners in
question that KARAF spins up... Thanks.
was (Author: [email protected]):
I should also mention that the same issue exisits for the rmiServer, there
needs to be an option for rmiServerHost and rmiRegistryHost, not just
rmiRegistryHost to allow explicit binding to a specified interface for all
listeners in question that KARAF spins up... Thanks.
> Also make rmiRegistryHost configurable
> --------------------------------------
>
> Key: KARAF-581
> URL: https://issues.apache.org/jira/browse/KARAF-581
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-core
> Reporter: Andreas Pieber
> Fix For: 3.1.0
>
>
> As discussed here: [1] make rmiRegistryHost configurable as parameter.
> I think this issue will require the following steps:
> * this have to be done in org.apache.karaf.management.RmiRegistryFactory.
> * In addition the blueprint and config have to be updated.
> * I assume that the felix webclient also have to be updated for this
> [1]
> http://mail-archives.apache.org/mod_mbox/karaf-user/201104.mbox/%[email protected]%3E
--
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
