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 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).
|