> Well, it may not be easy to "isolate" without turning debugging on. I am in > the camp who have far too much debug statements turned on "always" to have a > chance to figure out "what went wrong" afterwards. Of course, sometimes that > is not feasible, and that is when the dynamic settings of Level is useful.
This can be debated for years, and sure it will be ! Whatever, let's stop this discussion : I admit that those are valid points. Let's not use DEBUG, the gain is so small that it's much more a theorical question to use it against using "if (log.isDebugEnabled())" > The "logger.isDebugEnabled()" is cheap enough to be used for each invocation, > and provides the possibility for dynamic level settings in the logging > system. I fully agree. Being pragmatic helps a lot, when in production ;-)
