4 Replies Latest reply on Mar 18, 2008 12:10 PM by adrian.brock

    Configurator and MethodJoinpoints replacement

    alesj

      I need a replacement for MethodJoinpoint in
      - Configurator::getPropertyGetterJoinPoint
      - Configurator::getPropertySetterJoinPoint
      since it requires getter/setter to create MethodJoinpoint, which we obviously don't have with the FieldsPropertyInfo.

      Something like PropertyJoinpoint?

        • 1. Re: Configurator and MethodJoinpoints replacement
          alesj

          Or I can use the PropertyInfo.getFieldInfo and use this API from JoinpointFactory:

           FieldGetJoinpoint getFieldGetJoinpoint(FieldInfo fieldInfo) throws JoinpointException;
          
           FieldSetJoinpoint getFieldSetJoinpoint(FieldInfo fieldInfo) throws JoinpointException;
          

          Again ugly, but effective.

          • 2. Re: Configurator and MethodJoinpoints replacement

            No this goes back to the configurator tidyup task you just closed.

            These methods are no longer used except by the obsolete "OldConfigureAction".

            They should have been removed (and so should the obsolete action).

            • 3. Re: Configurator and MethodJoinpoints replacement
              alesj

               

              "adrian@jboss.org" wrote:
              No this goes back to the configurator tidyup task you just closed.

              These methods are no longer used except by the obsolete "OldConfigureAction".

              They should have been removed (and so should the obsolete action).

              OK, I'll reopen the task then.

              So, what exactly has to go out of Configurator then?
              Since I had no idea tidyup involved that part.

              • 4. Re: Configurator and MethodJoinpoints replacement

                 

                "alesj" wrote:

                So, what exactly has to go out of Configurator then?
                Since I had no idea tidyup involved that part.


                The idea was to reduce it to what actually gets used
                and to make it more comprehensible (if possible).

                Its just a helper class that's been through so many iterations that there's
                all sorts of unused cruft in there.

                The property stuff has long since changed to a get/set on the Bean/PropertyInfo
                but that doesn't mean the Configurator knew this. :-)