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 31908 invoked from network); 27 Aug 2003 23:24:10 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 27 Aug 2003 23:24:10 -0000 Received: (qmail 2248 invoked by uid 50); 27 Aug 2003 23:27:02 -0000 Date: 27 Aug 2003 23:27:02 -0000 Message-ID: <20030827232702.2247.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 dirk.verbeeck@pandora.be 2003-08-27 23:27 ------- I don't think we should add commons-logging. The "Abandoned" function should be considered for development only. It should only be enabled when your application is broken and is loosing connections. That is why I added those lines to the constructor (as a warning). The warning+default in BasicDataSourceFactory can be changed to an exception. JOCLContentHandler has a test main method with the offending statement. Don't know about the other ones.