RE: [Springframework-developer] AOP API

[Kopylenko, D. <dko...@ac...>]

Now I think the "disarray" is sorted in my head :-)
+1 for Advice model

Regards,
Dmitriy.

-----Original Message-----
From: Rod Johnson [mailto:rod...@in...] 
Sent: Friday, November 07, 2003 3:08 PM
To: spr...@li...
Subject: Re: [Springframework-developer] AOP API


> 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.

That was my original reason (that AspectJ advice is both pointcut and code).

"Advice" is nice and simple.

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/springframework-developer