Re: [aspectj-users] To LTW or not to LTW? :-)

["Wes" <wes@xxxxxxxxxxxxxx>]

New people typically learn the AspectJ language using AJDT at compile time, 
because it provides such great support for understanding the crosscutting 
structure.  You get some IDE feedback rather than having to test the program.
That's also how experts work through aspect design issues, more interactively.

LTW is a great way to deliver binary aspects.  Just give the aspect jar files
to your users and tell the users how to set up LTW.  It's essential if they 
don't want to change their build environment, so long as you don't mind 
absorbing the time/space costs of weaving at runtime.

There are many other considerations, but those are the dominant ones.

hth - Wes

> ------------Original Message------------
> From: nlif <naaman@xxxxxxxxxxx>
> To: aspectj-users@xxxxxxxxxxx
> Date: Sun, Oct-8-2006 3:08 AM
> Subject: [aspectj-users] To LTW or not to LTW? :-)
>
> 
> Hi,
> 
> I'm new to AspectJ. I'm using it via Spring 2.0, and I'd like to 
> understand
> the pros and cons of using LTW compared to compile-time weaving. Are 
> there
> certain scenarios for which one is more suited than the other? What are 
> the
> considerations?
> 
> Please advise.
> 
> Thanks,
> Naaman
> -- 
> View this message in context: 
> http://www.nabble.com/To-LTW-or-not-to-LTW--%3A-%29-tf2388608.html#a6659196
> Sent from the AspectJ - users mailing list archive at Nabble.com.
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>