2 Replies Latest reply on Jul 16, 2008 7:21 AM by Kabir Khan

    @InstanceAnnotation

    Kabir Khan Master

      As mentioned here:
      http://www.jboss.com/index.html?module=bb&op=viewforum&f=204
      and http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141090#4141090 I did not like the use of @InstanceAnnotation to dictate the behaviour of the proxyfactory. What I have done locally is to make AOPConstructorJoinPoint stop doing the check, and to pass in all per instance metadata to the proxy factory. The check inside the proxy factory used to be blindly to create a proxy if there is metadata present. The new check checks if there is instance metadata present, and if so checks if the resulting instance advisor has more aspects than the class advisor. If there is, then we return a proxy. If the instance metadata does not mean any more bindings or interface introductions are matched, then we return the original object.

      This is all sitting locally on my machine. I had to make a few minor changes to the aop-mc-int tests to to get this working. The main thing not workin is the HasInstanceAnnotationTestCase which I think should be retired. This is all ready to commit unless anybody has some objections?