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

Claus Ibsen updated CAMEL-6972:
-------------------------------

    Attachment: after3.png

after3, we now have beautify mbean names in OSGi where we only use the 
symbolicName by default, and in case of a clash (eg when 2+ versions of same 
bundle co-exists) we use the counter pattern.

And we check the OSGi ServiceRegistry for name clash of the <camelContext> id 
as well, so we can auto assign their names as

- camel-1
- camel-2
- camel-3
- ...



> JMX MBean naming - Use symbolicName instead of bundleId as default for OSGi 
> naming
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-6972
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6972
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, jmx
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.13.0
>
>         Attachments: after.png, after2.png, after3.png, before.png
>
>
> Now that we have removed the hostname from the JMX naming, lets improve 
> another one, to use the symbolicName instead of bundleId as prefix for the 
> mbean names in Karaf/SMX.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to