2 Replies Latest reply on Oct 14, 2002 8:37 AM by adrian.brock

    Standard question about JMX: JMX vs Reflexion

    balteo

      Hello,
      I am trying to establish a comparison of Java Management Extensions and Java Reflexion. What does JMX brings that "standard" reflexion cannot do? What is the difference between those two APIs and what would be a practical use case for them?
      Thanks in advance,
      Balteo.

        • 1. Re: Standard question about JMX: JMX vs Reflexion
          prabhakar

          They are used for quite different purposes. JMX is a standardized way to manage your components and instrument them. Reflection is a way to dynamically discover things about a class at runtime.

          -prabhakar

          • 2. Re: Standard question about JMX: JMX vs Reflexion

            Yes JMX was originally intended for dynamic management of applications.

            It is used within JBoss to provide de-coupling of
            services.

            You can think of it as reflection based on identity,
            rather than reference. The implementing object can
            change but your ObjectName is still valid.

            Also, the invocation is detyped, it is not based
            on interfaces. Although Standard MBeans and MBean
            proxies provide an easy mechanism to reintroduce
            interfaces without losing the decoupling.

            Regards,
            Adrian