> > 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. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
