Oliver,
this might have been discussed before... anyway, any reason not to migrate to using Commons-Logging, which already includes adapters for Log4J, JDK1.4 and the Avalon Logkit?
Well, it has been discussed before and we even had a vote that said:
Logging API will be augmented by a method allowing for both message and
throwable in one call. A general redesign of logging is deferred to
later releases.
Anyway, for later releases, here is my comment: I have tried commons-logging and it seems to have a very strong bias towards log4j. It seemed to me if there is log4j anywhere in the classpath it will use this, even though the user might want to use other logging implementations.
Every more severe is the need to touch (at least that's what I understand) every spot in the code that does logging. That's pretty much of an impact. So, the discussion could be "is it worth it"?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
