camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CAMEL-3288) Allow option to let end user set a custom naming strategy for JMX naming CamelContext
Date Tue, 09 Nov 2010 14:53:00 GMT

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

Claus Ibsen reassigned CAMEL-3288:
----------------------------------

    Assignee: Claus Ibsen

> 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
>            Assignee: 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.


Mime
View raw message