Hi Scott, On 19 February 2010 08:59, Scott Bartram <[email protected]> wrote: > Does AspectJ 1.6.8 work OK with Spring 2.5.6? I'd really like to decrease > the current memory footprint (> 100MB) in our application with AspectJ 1.6.4.
Interesting you should ask that! Last week we were testing 1.6.8 with Spring 2.5.X and Spring 3.0.X. With Spring 3.0 it works fine, with Spring 2.5 I've had one problem reported but been unable to recreate the issue myself. There is no reason I know of why it shouldnt work. > Is there a way to turn on the pointcut profiling messages when just using > Spring AOP (no ajc or LTW) in a JBoss container? Hmm, this is possible if the right set of options could be passed to the weaver to set it up. However, I think it is probably of limited usefulness given that Spring AOP only supports execution join points. Per the articles I wrote on performance, method-execution matching is one of the most optimized areas, so I'd hope with 1.6.8 you wouldn't see any slowness that would need profiling :) If you truly think there is slowness there, post upgrade to 1.6.8, I can do a bit of digging to see how the options might be passed. cheers, Andy _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
