commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22776] - DBCP should not be writing messages to stderr or stdout
Date Wed, 27 Aug 2003 23:27:02 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22776>.
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.

Mime
View raw message