As much as I respect Ceki, I do think that there is a place for commons-logging. It does provide a nice transition platform when you are switching out of JDK1.4-logging, because you were brain-dead at the time you chose it ;-).
It is also very useful for people writing commercial re-distributed applications, that want to allow for end-user flexibility on the real logging package. But read the article and decide for yourself. "Jacob Kjome" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I only have one thing to say about commons-logging... > > http://qos.ch/logging/thinkAgain.html > > Jake > > At 10:19 PM 2/11/2003 -0700, you wrote: > >This thread has already pointed this out indirectly, but I will go ahead > >and say it directly - you may want to consider the commons-logging API > >for your logging so that if (when?) you change logging implementation > >later you do not have to touch every class that does logging. > > > >The commons logging project does not provide a sophisticated logger, > >only a standard API for logging. If you change from JDK14 logging to > >Log4J, then to LogKit, then to the Next Big Cool Logger (tm), all of > >your code that does logging remains the same. You only have to configure > >the commons logging component to use the appropriate logger. > > > >It is *dirt simple* to use, and reasonably simple to set up - we did it > >in an afternoon. > > > >Larry > > > > >>> [EMAIL PROTECTED] 02/11/03 17:10 PM >>> > >Thanks Joe! > >I'll look into it. I've looked all over for some good info on Log4j but > >I can't find squat. > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
