RE: [Springframework-developer] AOP API

[renaud <re...@ao...>]

>=20
> >So I think that a fa=E7ade have to exist in the AOP Alliance=20
> interfaces.
>=20
> I'm not against the concept of having a facade in the AOP=20
> Alliance...if you're in favour of it that changes things a bit.

I always was. But I remember that most of the people were not sure,
especially because of the JSR-175.

> The idea was that the Invocation provides a way to guarantee=20
> the availability of the metadata information without tying in=20
> to Singletons or the like.

Umm, I see.

> However, I agree that in general=20
> metadata attributes are likely to be global. I do think that=20
> it should be possible to have other sources (like
> overrides) of metadata besides classes, so I don't think=20
> JSR-175 is a complete solution. Also it's way into the future.
>=20
> If we do have an AOP Alliance facade for attributes, how=20
> would we access it from pointcuts etc?

Well, since singletons are really not practical, maybe that I could go =
for
having some king of MetadataAware interface, like you suggested before.

Sthng like that?:

interface MetadataAware {
    MetadataFacade getMetadataFacade();
}

And:
MethodInvocation, Pointcut, ... extends MetadataAware

Renaud.

>=20
> Regards,
> Rod
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest=20
> developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV,=20
> and more! http://www.apachecon.com/=20
> _______________________________________________
> Springframework-developer mailing list=20
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20