Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread huntc
https://issues.apache.org/activemq/browse/CAMEL-1528 -- View this message in context: http://www.nabble.com/Naming-JMX-artifacts-from-Java-DSL-tp22986330p23033545.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread Claus Ibsen
On Tue, Apr 14, 2009 at 7:19 AM, huntc 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 > u

Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread huntc
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

Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread Claus Ibsen
On Tue, Apr 14, 2009 at 6:52 AM, huntc wrote: > > Hi Claus, > > .id would have been great - however it is deprecated and not part of v2. Does .id in 1.x do what you want in the JMX console? If so we can undo the @deprecation and add it back in 2.0. It was removed as a part of a cleanup in the DSL

Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread huntc
Hi Claus, .id would have been great - however it is deprecated and not part of v2. Kind regards, Christopher -- View this message in context: http://www.nabble.com/Naming-JMX-artifacts-from-Java-DSL-tp22986330p23033229.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.

Re: Naming JMX artifacts from Java DSL

2009-04-13 Thread Claus Ibsen
On Fri, Apr 10, 2009 at 12:59 PM, huntc wrote: > > Is there an easy way to name routes and processors when declaring them via > the Java DSL? I would like to see some more meaningful names displayed via > JMX. Hi There should be some .id, .description and .group DSLs you can use. > > Thanks. >