You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2003/09/20 17:14:50 UTC
DO NOT REPLY [Bug 22776] -
DBCP should not be writing messages to stderr or stdout
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
dirk.verbeeck@pandora.be changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From dirk.verbeeck@pandora.be 2003-09-20 15:14 -------
Like Shankar said, we should only add a dependency on a logging package if
really needed.
We could consider making more use of the logwriter on the datasource.
Or optionally provide a aspectj addon to do more detailed tracing/logging.
But that's another issue/enhancement...
DBCP should not be writing messages to stderr or stdout
Posted by "Noel J. Bergman" <no...@devtech.com>.
> DBCP should not be writing messages to stderr or stdout
> dirk.verbeeck@pandora.be changed:
> Resolution| |WONTFIX
> Like Shankar said, we should only add a dependency on a logging
> package if really needed.
> We could consider making more use of the logwriter on the datasource.
This should still be fixed. As you say, at the least make more use of the
logwriter. In the James code, I use an adapter subclass that bridges to
Avalon LogKit. The default in BasicDataSource is System.out, anyway.
DBCP is used in server applications. Logging is important. The reason why
so many logging packages appeared is because logging wasn't part of Java
from the beginning, and it IS important.
I ought not have to call System.setOut / System.setErr() in order to get
output logged. That would be a bad idea, anyway, without knowing that the
logging code doesn't use one of them to record a logging emergency.
--- Noel
DBCP should not be writing messages to stderr or stdout
Posted by "Noel J. Bergman" <no...@devtech.com>.
> DBCP should not be writing messages to stderr or stdout
> dirk.verbeeck@pandora.be changed:
> Resolution| |WONTFIX
> Like Shankar said, we should only add a dependency on a logging
> package if really needed.
> We could consider making more use of the logwriter on the datasource.
This should still be fixed. As you say, at the least make more use of the
logwriter. In the James code, I use an adapter subclass that bridges to
Avalon LogKit. The default in BasicDataSource is System.out, anyway.
DBCP is used in server applications. Logging is important. The reason why
so many logging packages appeared is because logging wasn't part of Java
from the beginning, and it IS important.
I ought not have to call System.setOut / System.setErr() in order to get
output logged. That would be a bad idea, anyway, without knowing that the
logging code doesn't use one of them to record a logging emergency.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org