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? 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.
