2 Replies Latest reply on Aug 16, 2007 6:59 AM by adrian.brock

    Need to revisit some other AOP integration

    adrian.brock Aug 14, 2007 11:59 AM

      Now that I've moved the aop classes out of the microcontainer bootstrap in jboss-head
      its showing we need to revisit the aop integration with the MC and JBossXB.

      The problem is that neither of the factory settings that sets up this integration
      can see the aop classes so the configuration is not done.

      I'm not sure what state aop and aop-mc-int are in, so I didn't want
      to update the snapshots for these. Instead I've hacked a horrible
      class that redoes the integration work:
      https://svn.jboss.org/repos/jbossas/trunk/system/src/main/org/jboss/aop/deployers/temp/Hack.java

      This obviously needs fixing to do be done in a more reasonable way. ;-)

      • 59892 Views
      • Tags:
        • 1. Re: Need to revisit some other AOP integration
          kabirkhan
          kabirkhan Aug 15, 2007 10:38 AM (in response to adrian.brock)

          aop + aop-mc-int should be pretty stable.

          Could we do something like the following?

          1) expose Property-/AbstractConfiguration as a bean, with settable JoinpointFactoryBuilder and DependencyBuilder properties
          2) declare the AOP flavours of JFB and DB as beans, which then are installed and override the ones in AbstractConfiguration. This would replace the first part of the hack.

          I am not sure where the AOPBeansSchemaInitializer was initialised in the "old" config?

            • Actions
          • 2. Re: Need to revisit some other AOP integration
            adrian.brock Aug 16, 2007 6:59 AM (in response to adrian.brock)

             

            "kabir.khan@jboss.com" wrote:
            aop + aop-mc-int should be pretty stable.

            Could we do something like the following?

            1) expose Property-/AbstractConfiguration as a bean, with settable JoinpointFactoryBuilder and DependencyBuilder properties
            2) declare the AOP flavours of JFB and DB as beans, which then are installed and override the ones in AbstractConfiguration. This would replace the first part of the hack.


            Only if there was a permission to change it, otherwise somebody could break the whole
            system by setting a broken builder (Denial of Service Attack).


            I am not sure where the AOPBeansSchemaInitializer was initialised in the "old" config?


            In the JBossXB project inside the Singleton resolver.
            But it ignores class names that it cannot find from the JBossXB classloader.

              • Actions