on 05-08-2009 1:35 PM
I'd like some suggestions on how to better utilize the debugger. I don't have my step filtering set up properly. I'd prefer to stay in just my code. I really don't care to step though each endless/mindless SAP/Java object - I want to walk my code.
What suggestions do you have to put in my step filtering and any other debug options in order to keep me in just my code.
Regards,
Diane
step filtering naviagtion path
Preferences->java->debug->step filtering
may be helpful.
Thanks,
Rama
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Diane,
I have around 4 years of experience in WD development. I used debugging very few times. The best way to find where the problem and what the problem is tracing. Use IWDMessageManager API to print the values of the attributes or messages like u201Centering into foru201D, u201Cinside ifu201D etc. The advantages of tracing are you can trace more number of attributes at any time and you can trace a particular block of your code directly.
Regards,
Siva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.