[Jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - Re: JBAOP-80 AOPJoinpointFactory

[<kab...@jb...>]

I get the opposite scenario from with a real annotation


  | @Test
  | public class Child extends Base
  | {
  |    public static boolean childInvoked;
  |    public void childOnly()
  |    {
  |       childInvoked = true;
  |    }
  |    
  |    public void baseOverridden()
  |    {
  |       childInvoked = true;
  |    }
  | }
  | 

In this scenario 

  | execution(* @org.jboss.test.microcontainer.support.Test->*(..))	
  | 

will not pick out Base.baseOnly(). This is similar to how "real" AOP works, although once the generated advisor weaving for AOP 2.0 is finalized it will be possible actually match on this.

I think it should be consistent whether we are advising with a proxy or a woven class - question is what way to go?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944882#3944882

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944882