RE: [Springframework-developer] AOP API

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

Well again, I am contradicting myself. If we follow AspecJ terminology,
Pointcuts should not have actual implementation of the concern only rules to
apply Advice to Joinpoints. But we don't have to strictly follow AspectJ.

Dmitriy.

-----Original Message-----
From: Kopylenko, Dmitry [mailto:dko...@ac...] 
Sent: Friday, November 07, 2003 2:38 PM
To: 'spr...@li...'
Subject: RE: [Springframework-developer] AOP API


Currently (in Spring) you could have a MethodPointcut (with an interceptor)
or MethodInterceptor without pointcut (well with AlwaysInvoked pointcut).
So, the same thing would be here, in an Aspect you would heve either
Pointcuts or Interceptors or both. The typical MethodPointcut would look
like this:

 public MyMethodPointcut implements StaticMethodPointcut extends
TransactionInterceptor{} or

 public MyMethodPointcut implements StaticMethodPointcut,
MethodInterceptor{}

If I am way off in my thinking, I'll stick with Rod's proposal.

Regards,
Dmitriy.
 
 
                 

-----Original Message-----
From: renaud [mailto:re...@ao...] 
Sent: Friday, November 07, 2003 2:21 PM
To: spr...@li...
Subject: RE: [Springframework-developer] AOP API



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



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