[Springframework-developer] Revised AOP API proposal

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

All,

Here's a variant on the API API which goes down the path initially suggested
by Renaud with separate class and method designators. Apart from that it's
much the same: Advice is still almost the same.

The unit of composition is a ClassFilter or MethodMatcher. The new Pointcut
interface allows for FieldMatchers in the future.

Abstract convenience classes could make it easy to use: for example, the
RegexpPointcut could continue to implement Pointcut, with no need for the
application developer to work with a distinct ClassFilter or MethodMatcher.
I think the only downside of this proposal is ease of use, and convenience
classes can resolve that.

This also enables IntroductionAdvice to have only a ClassFilter, as Bob
wanted.

Static methods are still used to "compose" pointcuts and the finer-grained
units of composition.

Feedback please... This is an important API to get right, and time is
closing now, as we don't want this to delay M3.

Regards,
Rod