On Tue, 3 Jun 2003, Adam Jack wrote:
Date: Tue, 3 Jun 2003 15:00:55 -0600
From: Adam Jack [EMAIL PROTECTED]
Reply-To: Jakarta Commons Users List [EMAIL PROTECTED],
[EMAIL PROTECTED]
To: 'Jakarta Commons Users List' [EMAIL PROTECTED]
Subject: RE: [Logging] What I find unfriendly about
In the very early days of C-L, you probably did need to do this ... it
took until 1.0.3 to get all the multi-class-loader kinks out. Please try
it with the current version of C-L.
Yeah, I recall those classloader woes (my app server, Sybase EAS, validly
returns null for a classloader I had
Commons-Logging important to protect open source projects from the turmoil
of JDK1.4 logging verse (the superior) log4j. That said, C-L is a
pain-in-the-rear. Just in case this isn't common knowledge (no pun intended)
I will one last time post my views let this drop.
I consider myself log
On Tue, 3 Jun 2003, Adam Jack wrote:
Further, the defaults seem terrible. If I run in JDK 1.4 (and have logging
configured) and C-L picks up the JDK1.4 driver, then I ought not need a C-L
properties file to see log messages. IMHO whatever the underlying
configuration has set-up, ought be
