|
From: Eugene K. <eu...@pl...> - 2005-01-19 21:24:56
|
Rob Harrop wrote: You are right. It is in compiler extensions. Sorry for confusion. regards, Eugene > If I remember correctly, the support for AOP Alliance interfaces is > included with the 2.0 distribution of AW. Check out the article on this > subject at > http://www.theserverside.com/articles/article.tss?l=AspectWerkzP1 > > Rob > > Eugene Kuleshov wrote: > >> Rob, >> >>> AW provides support for executing any advice that uses the AOP >>> Alliance interfaces. You are correct in saying that we should be able >>> to use AW internally within Spring. >> >> >> >> It should be easy to implement some generic AW-based wrapper for >> aopalliance interfaces, but I wonder if you can send me a link to an >> existing one. >> >> Thank you. >> >> Eugene >> >> >>> Rob >>> >>> Eugene Kuleshov wrote: >>> >>>> Michael, >>>> >>>> As far as I know, AspectWerkz is not using aopalliance interfaces, >>>> but you should be able to use AW as AOP container for Spring already. >>>> >>>> regards, >>>> Eugene >>>> >>>> >>>>> Most people in here probably have already read the news [*]. >>>>> AspectJ and AspectWerkz are merging. My understanding is that they >>>>> intend to frontends, AJ-style language-based and AW-style >>>>> annotation-based, to an enhanced common backend. >>>>> >>>>> Now, this might be a delicate issue, but I'll put it bluntly >>>>> nevertheless: Would there be a point in further consolidation with >>>>> Spring AOP? Spring already supports AspectJ besides its own AOP >>>>> variant; Spring and AspectWerkz already have aopalliance interfaces >>>>> in common. >>>>> >>>>> Michael >>>>> >>>>> >>>>> [*] >>>>> http://www.theserverside.com/news/thread.tss?thread_id=31244 >>>>> http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/aspectj-home/aj5announce.html >>>>> |