3 Replies Latest reply on Sep 21, 2007 9:01 AM by Adrian Brock

    aspect library config for jbossas

    Adrian Brock Master

      Related to this:
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083964#4083964
      and JBAS-4717

      I wanted to change the config for the @JMX aspect, but currently this config
      is defined in the aop project, so it would need a new release of aop to change it????
      I've moved it to the aspects project in the appserver codebase.

        • 1. Re: aspect library config for jbossas
          Kabir Khan Master

          The upgrade to the ServiceControllerLifecycleCallback breaks these tests:
          org.jboss.test.aop.test.MicrocontainerDefaultAnnotationUnitTestCase
          org.jboss.test.aop.test.MicrocontainerJMXUnitTestCase

          They run fine with the old JMXLifecycleCallback.

          • 2. Re: aspect library config for jbossas
            Adrian Brock Master

            The first problem is because the POJO names are the same as the JMX names.

            With the new ServiceController implementation, the JMX objects are real contexts
            in the MC that you can depend upon. i.e. they go through the ServiceController
            lifecycle.

            I don't understand the second test.
            It says jboss.aop:name=BeanWithDependency should not have been found?

            The only difference between the old and the new JMX lifecycle is the
            service controller lifecycle is now invoked for the MBean.
            But this test is NOT looking at the lifecycle it is just looking for the registered MBean,
            there has been no change to this.

            • 3. Re: aspect library config for jbossas
              Adrian Brock Master

               

              "adrian@jboss.org" wrote:

              The only difference between the old and the new JMX lifecycle is the
              service controller lifecycle is now invoked for the MBean.
              But this test is NOT looking at the lifecycle it is just looking for the registered MBean,
              there has been no change to this.


              i.e. the registerMBean() is still in the same place.