[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [aspectj-users] Requesting more info on Implementation Notes about perthis (compile-time vs. load-time weaving)
|
"A class loader may only weave classes that it defines. It may not
weave classes loaded by a delegate or parent class loader."
http://www.eclipse.org/aspectj/doc/released/devguide/ltw-rules.html
I.e., the code controlled during LTW is the set of classes defined
by the weaving class loader.
Wes
> ------------Original Message------------
> From: G Balaji <gopinathanbalaji@xxxxxxxxx>
> To: aspectj-users@xxxxxxxxxxx
> Date: Tue, Sep-26-2006 7:11 AM
> Subject: [aspectj-users] Requesting more info on Implementation Notes about perthis (compile-time vs. load-time weaving)
>
> Dear AspectJ Experts,
>
> From the AspectJ's programming guide's implementation notes [found at
> http://www.eclipse.org/aspectj/doc/released/progguide/implementation.html ] :
>
> "Aspects that are defined perthis or pertarget also have restrictions
> based on control of the code. In particular, at a join point where the
> bytecode for the currently executing object is not available, an aspect
> defined perthis of that join point will not be associated. So aspects
> defined perthis(Object) will not create aspect instances for every
> object unless Object is part of the compile. Similar restrictions apply to
> pertarget aspects. "
>
> In the context of the above statement, if we examine the following
> statement-fragment:
>
> "..aspects defined perthis(Object) will not create aspect instances for
> every object unless Object is part of the compile..".
>
> how is this statement affected when load-time weaving is used instead
> of (or, in addition to) compile-time weaving?
>
> Thanks,
> G Balaji.
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>