|
From: renaud <re...@ao...> - 2003-11-07 19:21:36
|
> Well, following AspectJ terminology the Advice is the
> construct that implements the crosscutting behavior
> (Interceptor in our case) and Aspect is the collection of
> Advice and Pointcuts. But Pointcut _is not_ Advice. So, how about:
>
> public interfce Advice{}
>
> public interface Interceptor extends Advice{}
>
> public interface Aspect {
> Advice[] getAdvice();
> Pointcut[] getPointcut();
> }
That's close to my first draft, but how do you link advice and pointcuts
then??
As I said in my previous email, Rod's proposal gets my vote for the moment.
Regards,
Renaud.
>
> Regards,
> Dmitriy.
>
> -----Original Message-----
> From: renaud [mailto:re...@ao...]
> Sent: Friday, November 07, 2003 2:02 PM
> To: spr...@li...
> Subject: RE: [Springframework-developer] AOP API
>
>
> >
> > > > public interface Advice {
> > > > getInterceptor();
> > > > getPointcut();
> > > > }
> > >
> > > I agree with the construct here and I like it. However, the
> > > terminology is quite confusing. It does not stick with usual AOP
> > > terminology (e.g. AspectJ).
> > >
> > > What about (random thought):
> > >
> > > public interface AdvisedPointcut {
> > > getInterceptor();
> > > getPointcut();
> > > }
> >
> > I'm open to suggestions as to naming. AdvisedPointcut makes sense,
> > but didn't initially appeal to me.
> >
> > AspectElement? To make it clear that it could be a unit of
> composition
> > in more complex aspects (as in the additional Aspect interface I
> > proposed).
>
> Ummm...
> Having a second thought, I was wrong. Advice makes sense
> within the AOP terminology. If you look at AspectJ, your
> advice contains a pointcut *and* a code (the interceptor
> part) -- the idea is that you can have abstract pointcuts
> that you can then refine in subclasses of the aspects.
>
> So, finally, I like very much:
>
> public interface Advice {
> getInterceptor();
> getPointcut();
> }
>
> And of course the subsequent:
>
> public interface Aspect {
> Advice[] getAdvice();
> }
>
> +1 for me.
>
> Renaud.
>
>
> >
> > Regards,
> > Rod
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: ApacheCon 2003,
> > 16-19 November in Las Vegas. Learn firsthand the latest
> developments
> > in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more!
> > http://www.apachecon.com/
> > _______________________________________________
> > Springframework-developer mailing list
> > Spr...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/s> pringframework-developer
> >
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV,
> and more! http://www.apachecon.com/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: ApacheCon 2003,
> 16-19 November in Las Vegas. Learn firsthand the latest
> developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV,
> and more! http://www.apachecon.com/
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
|