On Tue, Apr 14, 2009 at 7:19 AM, huntc <hu...@mac.com> wrote: > > Hi Claus, > > Yes, .id does exactly what I need. I think it is a useful method to keep as > JMX is almost unusable without it - you have to trawl so many nodes.... > > In fact, I'd go as far as stating that I wouldn't bother creating a JMX node > unless the programmer identifies it. If the node is important to them then > they'll take a few seconds to name it... > > Perhaps the same for endpoints, processors etc... > > What'd think? Good idea. However there should be an option in the camel configuration that enables this behaviour and it should be off by default. Then if you want to only show certain nodes then you can assign them an id and enable this option.
Feel free to create a JIRA for this feature. And remeber to mention that the .id should be added again from 1.x And if you have a good suggestion for the option name :) > > Kind regards, > Christopher > > -- > View this message in context: > http://www.nabble.com/Naming-JMX-artifacts-from-Java-DSL-tp22986330p23033407.html > Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
