| In general you build an application once, and run it many times. Load-time weaving means you pay the cost of weaving every time your application launches. If you do post-compile time weaving as part of your build process, then there will be no overhead at runtime and your application will start faster and use less memory. So I would always opt for post-compile time weaving unless:
* you need the flexibility of changing the set of aspects you are using from run to run * you are using the aspects for temporary instrumentation (e.g. using Glassbox) - this is really a special case of the above * you just want to try things out quickly and don't want the hassle of changing your build process
Load-time weaving can also sometimes be beneficial in speeding up certain development scenarios. In general however, why do at runtime what you could easily have done ahead of time...
Hi,
I was analysing whether one should go for Post-compile weaving or Load-time weaving. I read on the bea site (http://dev2dev.bea.com/pub/a/2005/08/jvm_aop_1.html) that Load-time weaving (using agents) affects both scalability and usability. Are these issues of scalability and usability applicable to post-compile weaving as well?
Any help on the technical advantage of one over another would be highly appreciated.
Thanks,
Virender Singh,
Consulting and Architecture Team,
HSBC GLT, Pune , India
************************************************************
HSBC Software Development (India) Pvt Ltd
HSBC Center Riverside,West Avenue ,
25 B Kalyani Nagar Pune 411 006 INDIA
Telephone: +91 20 26683000
Fax: +91 20 26681030
************************************************************
*******************************************************************
This e-mail is confidential. It may also be legally privileged.
If you are not the addressee you may not copy, forward, disclose
or use any part of it. If you have received this message in error,
please delete it and all copies from your system and notify the
sender immediately by return e-mail.
Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
*******************************************************************
"SAVE PAPER - THINK BEFORE YOU PRINT!"
_______________________________________________ aspectj-users mailing list
|
