[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Runtime weaving without agent
|
No, it is not more efficient. But not as much less efficient as you might fear - and much more flexible. You can (de)activate your advice without recompilation, reweaving, redeployment. You can even change the "if" condition during runtime if you like.
Having said that, I do not know if this is what you need or want. It was just a suggestion.
Alexander Kriegisch
Am 12.04.2013 um 10:57 schrieb Eric Chatellier <chatellier@xxxxxxxxxxxxx>:
> Le 08/04/2013 19:31, Alexander Kriegisch a écrit :
>> How about compile-time weaving aspects and (de-)activating them using if() pointcuts? Try not to overcomplicate your setup, keep it simple.
> I will take a look.
>
> But, It is more efficient to have a class with if aspects than a non weaved class?
>
> --
> Éric Chatellier - Code Lutin
> Tel: 02.40.50.29.28 - http://www.codelutin.com
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
