Re: [Springframework-developer] AOP API

[Rod J. <rod...@in...>]

> Having a second thought, I was wrong. Advice makes sense within the AOP
> terminology. If you look at AspectJ, your advice contains a pointcut *and*
a
> code (the interceptor part) -- the idea is that you can have abstract
> pointcuts that you can then refine in subclasses of the aspects.
>
> So, finally, I like very much:
>
> public interface Advice {
>     getInterceptor();
>     getPointcut();
> }
>
> And of course the subsequent:
>
> public interface Aspect {
>     Advice[] getAdvice();
> }
>
> +1 for me.

That was my original reason (that AspectJ advice is both pointcut and code).

"Advice" is nice and simple.

Regards,
Rod