camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject Re: [Discuss] How to do JMX in Apache Camel?
Date Mon, 24 Oct 2011 09:02:29 GMT
Yes as people will want the interfaces anyway to conveniently call the 
beans we can also use them to construct the mbeans.
So at the moment the annotations only give us the bonus of adding 
documentation. So of course it would be great to have both
documentation and interface but currently this does not work.


Am 23.10.2011 10:15, schrieb Claus Ibsen:
>> Exactly if you create the MXBeans using interfaces named ClasNameMXBean then
>> the JDK knows how to instantiate the MXBean and the user can use this
>> interface for proxies.
> The only compelling reason IMHO for doing this is because it allows
> Camel end users to use those interfaces, to access the Camel MBeans.
> But using the interfaces we lose the ability to add meta-data to the
> JMX such as the description. If you use JConsole and hover the mouse
> on an attribute
> etc. then there is a label that shows the description etc. Likewise
> 3rd party tooling can show those descriptions as well.
> Besides description there is also some other less used meta-data we
> could possible add in the future.
> That said, we could possible use the MXBean in camel-core, which
> allows Camel end users as a client more easily to access the Camel
> MBeans using
> those interfaces in their client API. As mentioned before there is a
> JIRA ticket about this (interfaces for MBean). So possible name those
> interfaces accordingly
> to MXBean.
> The MBean can still be enlisted in JMX server using the annotations,
> which means we still get the description meta-data, and possible get
> best of both worlds.

Christian Schneider

Open Source Architect
Talend Application Integration Division

View raw message