3 Replies Latest reply on Feb 5, 2002 8:26 AM by Juha Lindfors

    ModelMBeanAdapter impl

    Trevor Squires Novice


      Hey,

      I just wanted to check that this was ok:

      The ModelMBeanAdapter (MMBA) is constructed from a managed resource instance and an MMBInfo object. The MMBA only is ony concerned about how to set-up and route attribute and operation calls to a relevant Provider.

      I expect that all interceptors will sit in front of the MMBA. i.e. between the RequiredModelMBean or XMBean and the MMBA.

      Ok?
      Trev

        • 1. Re: ModelMBeanAdapter impl
          Trevor Squires Novice

          Another issue on this:

          When I resolve an MMBOpInfo signature to a Method object I need to interact with a classloader.

          I've lifted getSignatureAsClassArray from the soon to be defunct StandardMBeanInterceptor. However it seems that it's delegating to the DefaultLoaderRepository on CNFExceptions.

          IMHO it's impossible that the construction of an MMBA will rely on the DefaultLoaderRepository. The managedResource instance's classloader will always be able to resolve a class passed as a parameter to a method call.

          I just want to make sure that this assumption is correct and I'm not forgetting something about JBoss's wacked-out classloaders.

          Thoughts?
          Trev

          • 2. Re: ModelMBeanAdapter impl
            Juha Lindfors Master

            >
            > I expect that all interceptors will sit in front
            > of
            the MMBA. i.e. between the RequiredModelMBean
            > or XMBean and the MMBA.
            >
            > Ok?

            yup

            The MMBA should be pluggable so that the reflection based implementation can be replaced with a specific class implementation (DynamicMBean style) that allows for fast invocations with MMB as well.

            • 3. Re: ModelMBeanAdapter impl
              Juha Lindfors Master

              > I just want to make sure that this assumption is
              > correct and I'm not forgetting something about
              > JBoss's wacked-out classloaders.

              I think you are correct.

              -- Juha