[Springframework-developer] AOP Alliance

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

Nearly forgot. About our release plan, the AOP Alliance appears to be
springing back to life (no pun intended).

The guys behind AOPI--another SF AOP integration project--want to join AOP
Alliance. Jon Tirsen has suggested changing the current interface names to
use more standard AOP terminology:

> Regarding the current AOP Alliance APIs: Maybe we should try to move
> away a bit from the J2EE-things and adapt a little more standard AOP
> terminology? For example replace Interceptor with Advice and Invocation
> with JoinPoint. I rather like the names in AspectWerkz:
> Interceptor+MethodInterceptor -> Advice
> Invocation+MethodInvocation -> JoinPoint+MethodJoinPoint
> The interesting thing is that you could for example implement an advice
> that polymorphically works as field-advice, method-advice,
> instantiation-advice and so on.

We can do this easily enough, but it would mean a refactoring in Spring.

Thoughts? I'm inclined to agree with Jon about the standardization benefits,
but I must admit I find the "J2EE-centric" interceptor terminology clearer.
I'm try to canvas opinion on this ASAP.

The *functionality* of the AOP Alliance APIs won't be changing soon. As
Spring is approaching release, and is the only implementation at present,
our release plans definitely constrain AOP Alliance right now.

Regards,
Rod