1 Reply Latest reply on Mar 13, 2006 7:20 PM by Adrian Brock

    Using our own ModelMBeanInfoSupport

    Adrian Brock Master

      I've been meaning to do this for a while because the ModelMBeanInfo impl classes are significantly slower than the JBossMX versions.

      But it looks like it is also needed to avoid non serializable
      objects put in the descriptor breaking the getMBeanInfo()
      operations for remote access.
      See the RMIAdaptorUnitTestCase when run with JDK5

      The idea would be move the classes to org.jboss.mx.modelmbean
      then have the javax.management.modelmbean classes extend them,
      e.g.

      package javax.management.modelmbean;
      public class ModelMBeanInfoSupport extends JBossModelMBeanInfoSupport
      


      My only qualm is whether this would still pass the JMX signature tests
      in the TCK.

        • 1. Re: Using our own ModelMBeanInfoSupport
          Adrian Brock Master

          Actually, we cannot replace the whole of ModelMBeanInfoSupport.

          My suggestion above won't work because it will break
          serialization compatibility.

          We can't use an alternate implementation because not all
          the classes are interfaces.

          I think we can still use our DescriptorSupport code
          to get the serialization fix and performance improvements.
          But I'll probably have to introduce
          some kind of compatiblity mode for older versions that don't
          have the new class on the client or use writeReplace()?