[jira] [Resolved] (KARAF-4123) Provide a more dynamic default for serviceUrl configuration

["Gert Vanthienen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen resolved KARAF-4123.
------------------------------------
    Resolution: Fixed

Fixed for the {{karaf-2.x}} branch in https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=e3a6ed118d4595db6ae1df948538e6727fbab663
Fixed for the {{karaf-3.0.x}} branch in https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commit;h=05c690ffd8afbf515c31b21889b62348a11e46d3

> Provide a more dynamic default for serviceUrl configuration
> -----------------------------------------------------------
>
>                 Key: KARAF-4123
>                 URL: https://issues.apache.org/jira/browse/KARAF-4123
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-management
>    Affects Versions: 2.4.3, 3.0.5
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 2.4.4, 3.0.6
>
>
> The default value for {{serviceUrl}} in the {{org.apache.karaf.management}} PID is now defined as 
> {noformat}
> service:jmx:rmi://localhost:44444/jndi/rmi://localhost:1099/karaf-$[karaf.name]
> {noformat}
> Blueprint's ConfigAdmin support does allow us to use replacement variables in those defaults too, so it would be nice to reuse the {{rmiServerHost}}, {{rmiServerPort}}, {{rmiRegistryHost}} and {{rmiRegistryPort}} values.
> (This issue is only relevant for Karaf 2.4.x and 3.0.x - in 4.0.x the code already behaves this way)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)