[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[aspectj-users] Runtime behaviour, error tracking and performance problems
|
Hi!
I think AOP is a great concept to separate crosscutting concerns! But I still have some questions concerning the runtime behaviour and the tracking of errors at runtime:
If you encounter performance problems or errors while you are using a program that was implemented using AspectJ, is it a problem that the performance problems or errors may refer to the code generated by the weaver and not to the source code that I have written?
How can I trace back especially performance weaknesses which are (or may be) based on the weaved code?
And what is your experience: Are the debuggers which AspectJ and AJDT offer sufficient to find the cause for errors which happen at runtime?
Or does AOP in general make it more difficult to find performance problems and errors because the failure could come from the java code, the AOP code or the weaved code?
Thanks for your help in advance!
Steffen
--
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm
