[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Rip out JBoss JMX implementation?

[adrian@jboss.org]

The reasons are - in order of current importance (rather than the original importance)

1) ClassLoading/UnifiedClassloader - should be gone soon with the new classloader

2) Thread ContextClassLoader is not set by other JMX implementations during
invocations on the MBean.

3) JMX Interceptors/XMBean - although this should work in any JMX, Scott broke it a while ago - the XMBean is now tied to the MBeanRegistry for some bizarre reason?

4) Ability to get the real object for any MBean - i.e. from the JBossMX MBeanRegistry
mostly used in Injection. It is still used in the CMP2 container IIRC.

5) Performance - Sun's RI is still slow - but it got better when they improved the
performance of reflection in JDK1.4

6) Bugs - The RI used to be very buggy, it's got better, 
but this is something that has recently come back to haunt us with not being able to
change/fix javax.management.* classes in JDK5+

7) Some parts of JBossAS use JBossMX specific details, like the classloading api
and the MBeanRegistry.

In practice, if (3) was fixed then we could move (2) into an XMBean interceptor
(where it belongs), and we'd probably still get some of the improved performance.

We already lost some performance switching to Sun's JDK5 javax.management.*
classes, notice the difference booting JBoss4.0 on JDK1.4 vs JDK5? :-)

I don't know how you solve (4) generically using the spec JMX api.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073898#4073898

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073898