Bill,
Yes, but why bother? I can just as easy add temporary printlns. The
name alone is a good reminder to strip them out before committing.
Adding log messages means they'd tend to be left in the code,
cluttering everything long after their usefulness passes.
Logging is *not* a debugging solution IMO. IMO, logging is for
informing customers of server state, not debugging one's logical
errors in code.
With the recursive problems in Logging early at startup, I was forced
to use something else, hence why I use AMXDebug, a much more useful
mechanism with fewer problems (for me at least).
Lloyd
On May 4, 2007, at 12:18 PM, Bill Shannon wrote:
> Lloyd L Chambers wrote:
>> Yes, except that we don't have one-off loggers for targeted
>> debugging. Turning it on for 'admin' is not helpful.
>
> Nothing prevents you from creating a Logger for just the class you
> want to debug.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>