Re: [Springframework-developer] AOP API proposal

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

I attach a proposal for a revised AOP API. (Use wordwrap.)

This incorporates several of Bob's suggestions, but isn't a radical
overturning of present Spring AOP concepts.

I think it achieves the following major goals:

- enable pointcut and interceptor reuse, independently
- support pointcut composition
- allow optimization by creating pointcuts that exclude whole classes
without the need to check at method level
- improve the introduction mechanism
- allow the packaging of multiple advices into an Aspect. (In the future;
I'm not planning to implement that now.)

I've already implemented it: this is not to mean that it's set in stone, but
that it's feasible.

Comments, please.

I think it's important that M3 has a new, and stable, AOP API. This means
that we have to finalize this in the next few days.

Regards,
Rod