[Springframework-developer] AOP API changes

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

All,

I've just committed the current version of the AOP proposal (#2).

All unit tests pass (naturally). However, there will be an impact on code
using the AOP API. Interceptors are unaffected, unless they relied on the
AttributeRegistry, now removed. Pointcuts _are_ affected. If you want the
old Pointcut concept (Interceptor + when to apply it) subclass
StaticMethodMatcherPointcutAdvice and it should work the same. The
RegexpPointcut is also pretty similar, but does need a reference to an
Interceptor now. (A subclass that also implemented Advice could easily add
this.)

The ProxyConfig API has changed significantly: code using this will also be
broken.

There's definitely scope for more abstract classes etc. to make the API more
usable. However, it is definitely more powerful now.

I'll be producing a migration guide from the old API.

I need to refine the comments considerably. (Help welcome!) I also need to
improve the tests for pointcut composition. Volunteers for any of these
tasks are welcome.

Please update from CVS and check your code ASAP. With M3 coming up, it's
important that we are all sure everything works. AOP transactions shouldn't
be affected, unless they did something fancy like provided their own
MethodPointcut (now Pointcut).

Regards,
Rod