You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/10/28 09:20:00 UTC

[jira] Updated: (CAMEL-3288) Allow option to let end user set a custom naming strategy for JMX naming CamelContext

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

Claus Ibsen updated CAMEL-3288:
-------------------------------

          Component/s: jmx
                       camel-core
             Priority: Minor  (was: Major)
    Affects Version/s: 2.4.0
        Fix Version/s: 2.6.0

> Allow option to let end user set a custom naming strategy for JMX naming CamelContext
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3288
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3288
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core, jmx
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> Look at NMR which got some code for picking an unique name
> http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/nmr/management/
> Consider moving the code to commonsman for reuse
> And at Camel add some flag to let end user have Camel append the bundle id for the CamelContext ObjectName in JMX so its always unique.
> And that you avoid Camel to fail starting a bundle if it has the same camelcontext id as an existing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.