Hi Eric, I'm not an expert on jmx, but I believe the original contributors of this code used mxbeans for a reason. In particular:
See this blog post by one of the authors of mxbeans:
"Going forward, it will generally be a good idea to write an MXBean wherever you would write a Standard MBean today."
"The MXBean concept provides a simple way to code an MBean that only references a predefined set of types, the ones defined by javax.management.openmbean. In this way, you can be sure that your MBean will be usable by any client, including remote clients, without any requirement that the client have access to model-specific classes representing the types of your MBeans."
"MXBeans in Java SE 6: Bundling Values without Special JMX Client Configurations recommends using MXBeans in any Java SE 6 application where Standard MBeans may have been used before moving to Java SE 6."
This blog post also shows that in some cases JMX UIs render the bean fields better with mxbeans than with std mbeans
Can you explain a bit about why ZooKeeper cannot be embedded into JBoss currently? Doesn't JBoss support MXBeans? This was standardized in java6, no? (that mxbeans are included in 1.6).
From what I read it seems like moving from mx -> standard mbeans is a step back. But I'd like to understand the problems seen with JBoss. If you can include some code/config that I could easily deploy into JBoss I'd be happy to try it out myself - perhaps we could include this in our testing regime so that we maintain compatibility going forward.
ps. we dropped java5 support in 3.1, we now only support java6, so the original description of the jira is stale. See