Generating DBCPEvents is the way to go.
No direct dependency on any logging library please.
The DBCP core should be able to run on a standard tomcat with no extra
logging requirments.
-- Dirk
Alex Karasulu wrote:
Steve,
Forgot to mention another added benefit of using a monitor (callback)
I've been looking through the DBCP source this morning and have noticed
several instances where System.out, System.err and printStackTrace()
have been used to write error or status messages to the console.
I'm wondering if there's any interest in a contribution that would
replace these calls with
Hi Steve,
-Original Message-
From: Viens, Steve [mailto:[EMAIL PROTECTED]
I've been looking through the DBCP source this morning and have noticed
several instances where System.out, System.err and printStackTrace()
have been used to write error or status messages to the console.
Karasulu [mailto:[EMAIL PROTECTED]
Sent: Monday, April 19, 2004 2:29 PM
To: 'Jakarta Commons Developers List'
Subject: RE: Replace System.out, System.err and printStackTrace() with
Commons Logging?
Hi Steve,
-Original Message-
From: Viens, Steve [mailto:[EMAIL PROTECTED]
I've
If you define a DBCPMonitor interface to announce notable events
you can leave the decision to have a dependency on logging up to
the user of the API. So DBCP does not need a commons-logging
dependency.
That would be easy to adapt to other logging packages, and would avoid the
sort of
