[
https://issues.apache.org/jira/browse/CAMEL-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-6972:
-------------------------------
Attachment: after2.png
after2 - we detect clashes in the osgi service registry on camel context name
as well, and use unique counter if clash detected, so we have
- camel = first auto assigned name in use
- camel-1 = if clash, then append -counter
- camel-2 = ....
Then we have nice clean auto assigned names in OSGi out of the box.
If people define the <camelContext id="foo"..> then that name is used instead
of just camel or camel-1, camel-2 etc.
> 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, 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)
