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 calls to the commons-logging package instead?
YES! :-)
At least on my part. Honestly, if you're going to tie Commons Pool and DBCP to Logging, also introduce the idea of levels so that we get debugging, info, error, etc., appropriate messages.
How would commons-logging fit within the Avalon framework? (James uses DBCP now).
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
