Re: [Springframework-developer] AOP API

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

>So I think that a façade have to exist in the AOP Alliance interfaces.

I'm not against the concept of having a facade in the AOP Alliance...if
you're in favour of it that changes things a bit.

> One problem with moving away with an AttributeRegistry
> concept on MethodInvocation is that we don't want Pointcuts
> to be dependent on Singleton magic (ie black magic) to get
> metadata: this should be easily pluggable at runtime. Perhaps
> a pointcuts interested in metadata could implement a
> MetadataAware interface and expose an Attributes property.

>However, I've never really understood the metadata attached to the
invocation. For me, metadata are set on the Java meta elements (classes,
fields, methods, ...). They do not depend on the invocation then.

The idea was that the Invocation provides a way to guarantee the
availability of the metadata information without tying in to Singletons or
the like. However, I agree that in general metadata attributes are likely to
be global. I do think that it should be possible to have other sources (like
overrides) of metadata besides classes, so I don't think JSR-175 is a
complete solution. Also it's way into the future.

If we do have an AOP Alliance facade for attributes, how would we access it
from pointcuts etc?

Regards,
Rod