Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 41267 invoked from network); 28 Aug 2003 00:45:20 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 28 Aug 2003 00:45:20 -0000 Received: (qmail 29341 invoked by uid 50); 28 Aug 2003 00:48:02 -0000 Date: 28 Aug 2003 00:48:02 -0000 Message-ID: <20030828004802.29340.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22776] - DBCP should not be writing messages to stderr or stdout X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22776 DBCP should not be writing messages to stderr or stdout ------- Additional Comments From shankar@cotagesoft.com 2003-08-28 00:48 ------- Argh. Changing this to use commons-logging also means fixes in the Tomcat distribution, and anyone else distributing DBCP. (Tomcat distributes commons-logging-api.jar, but not commons-logging.jar). Sigh! So the best thing is - just avoid logging stuff and thus avoid using commons-logging. Throw exceptions where possible. But some of the locations from where messages are printed are not amenable to throwing exceptions from (e.g. CPDSConnectionFactory.java).