[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Why are you using LTW?
|
I agree with Ramnivas. As an added benefit, if you're like me, you'll
see a big speed increase in your app when you move over to compile
time as well since runtime weaving can be costly.
On Feb 10, 2009, at 4:36 PM, Ramnivas Laddad wrote:
Most use LTW as an easy way to get started with AspectJ (no build
script modifications). A few also need to weave into container classes
and LTW seems easier than performing offline binary weaving and
replacing original jars with woven jars. If that is not required, many
eventually move over to compile-time weaving.
I wouldn't worry about "official" compiler issue, since in the end the
VM sees essentially the same byte code regardless of the utilized
weaving mechanism.
-Ramnivas
On Tue, Feb 10, 2009 at 1:40 PM, Wim Deblauwe
<wim.deblauwe@xxxxxxxxx> wrote:
Hi,
I was wondering why other people use LTW (Load Time Weaving)
instead of
compile time?
The main reason for me would be that with compile time you are not
using the
'official' compiler of Java. Is this something I should worry about
or is it
just paranoia on my side?
Another reason is that it seems attractive to be able to disable
aspects
when not needed, but so far I never felt the need to disable them.
I am now thinking on switching to compile time, mainly to be able
to do
'declare warning' and 'declare error', because I like to be able to
lay down
custom rules like this that are very specific to the project, but
are easily
enforced this way.
regards,
Wim
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
