Lots of people have used AspectJ for tracing. If you trace executions within your codebase you can typically get calling object info indirectly: look at the containing execution join point to see who made the call. This can work with tracing calls out to external code too. But if you only want a development aspect, I wouldn't be too concerned. Measure actual memory use when loaded in a VM to see the overhead. I believe a lot of the class file size overhead won't translate into memory overhead at runtime.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lee Sent: Thursday, November 02, 2006 11:25 AM To: [email protected] Subject: RE: [aspectj-users] Class file too big after aspect weaving Thanks for everyone who has responded. >>increase depends on how big your aspect code is, how small your original >>classes are and how many join points are found within your original code. My aspect code is relatively small but as I am capturing all calls, the aspect weaved code is getting bloated. >>not sure about the usefulness of such an aspect in production code It is only intended as a development aspect, not as a production aspect. >>Another thing to consider is advising executions instead of calls I want to use the trace to know the sequence of calls with the calling object info. So I need to capture calls instead of executions. Finally, has anyone really tried something like this? Larry. >From: "Ron Bodkin" <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: <[email protected]> >Subject: RE: [aspectj-users] Class file too big after aspect weaving >Date: Tue, 31 Oct 2006 09:15:49 -0800 > >Hi Lawrence, > >Another thing to consider is advising executions instead of calls, at least >excluding calls into your own packages. If you just want to trace methods, >it's a lot more efficient to do it once at method execution than everywhere >the method is called. > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lee >Sent: Tuesday, October 31, 2006 6:33 AM >To: [email protected] >Subject: [aspectj-users] Class file too big after aspect weaving > >Hi, > >I have a pointcut that captures all calls in my application and in the >advice, those method names and parameter names are logged to a file. > >When the above aspect is weaved into my application, the class file sizes >have increased 10 times in some cases. I am not sure how such a bloated ear >files affects the application server. I am afraid that I might get >OutOfMemoryError and haven't tried it on our server yet. > >I am not worried about the performance issues. It is ok if the application >runs slow as long as I don't get OutOfMemoryError. Just wondering if anyone >on this list has tried anything like this and if so, I would like to know >their experiences. > >Larry. > >_________________________________________________________________ >Experience Live Search from your PC or mobile device today. >http://www.live.com/?mkt=en-ca > >_______________________________________________ >aspectj-users mailing list >[email protected] >https://dev.eclipse.org/mailman/listinfo/aspectj-users > >_______________________________________________ >aspectj-users mailing list >[email protected] >https://dev.eclipse.org/mailman/listinfo/aspectj-users _________________________________________________________________ Ready for the world's first international mobile film festival celebrating the creative potential of today's youth? Check out Mobile Jam Fest for your a chance to WIN $10,000! www.mobilejamfest.com _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
