The reason for this is:
* support full dynamicity, e.g. aspect hot deployment and undeployment
(at runtime)
* still statically compile the code all the way (no reflection is used), and...
* optimize the chances of the code to be inlined by the JVM optimizing compiler
--
Jonas Bonér
http://jonasboner.comOn 8/22/07, Alexandre Vasseur <
avasseur@...> wrote:
> yes. for any joinpoint shadow, we JIT-generate a class that will
> invoke the actual advice(s).
> I think Michael Haupt (cc) did wrote a detailled analysis of this
> architecture in his work for for AOSD 2004 or 2005.
> Alex
>
> On 8/21/07, chris84 <
christoph_seemann@...> wrote:
> >
> > Hallo,
> > I write my thesis of AOP. My Question : Is that right that aspectwerkz do
> > not insert the advice in the code, but insert a method which called the
> > advices. I decompiled my application i see a method sounds like
> > JoinPointManager is this the method which called the advices?
> > Please help me it's the las chapter i need.
> >
> > Thank You.
> > Best Regards
> > Chris
> > --
> > View this message in context:
http://www.nabble.com/JoinPointManager-AspectWerkz-tf4304520.html#a12252605237> > Sent from the AspectWerkz - Dev mailing list archive at Nabble.com238.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> >
http://xircles.codehaus.org/manage_email239> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>
http://xircles.codehaus.org/manage_email240>
>