Hi,
Just wanted to get feedback on what most people think is better-
Logging: Includes any Log API/Methods you use
Debugging: Includes using Breakpoint, Step Into etc with Debugger
This is specifically from Java Viewpoint.
Thanks for your responses.
They are both very useful in the proper circumstance.
General logging gives you an easy way to see just what your code is
doing, and to log that it is, indeed, doing the right things when
running your unit tests.
Logging that includes timing, call count, other benchmarking options can
be a very good way to highlight strange behaviors in your code without
having to run a profiler on a customer machine.
A debugger is probably the best way to track down a single point failure
- bring the code up in the debugger, track down what it is doing at the
point of failure, examine needed variables, and fix the problem. Very
quick, and very efficient.
I have found debugging works better for WebObjects, but extensive
logging works better for most long executing code.
For me, the key questions are:
1. Will I be able to run a debugger on systems showing a problem.
2. Will I be able to run a profiler on systems showing a problem
3. Is my customer adept enough to run with a special extended logger
file in place to gather data I need.
4. Is logging lightweight enough to capture needed information on every
run, or must it be something only activated at need.
Scott