|
I am surprised that Ramnivas did not point out that you can in effect
have the best of both worlds with a hybrid solution which is extremely
powerful when dealing with aspect libraries for diagnostics and
resource monitoring as you can configure this without having to go
through a complete build cycle. Test and Ops teams do not like to see
two different versions of a library. http://www.infoq.com/news/2009/01/ramnivas-aop-choices JXInsight 5.6 extends it load-time weaving cache to now store the transformed bytecode image across application executions turning load-time weaving into binary weaving on consecutive executions. Our approach makes the switch between load-time weaving and binary weaving transparent - the first time an application is executed JXInsight will use load-time weaving the second time it uses binary weaving via the persisted transformed bytecode from the initial load-time weaving transformation. This reduces the (re)start-up time as well as the memory footprint - both which is extremely important in production environments. William Message: 1 Date: Fri, 13 Feb 2009 14:06:02 -0500 From: Dave Whittaker <[email protected]> Subject: Re: [aspectj-users] Why are you using LTW? To: [email protected]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: |
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
