I'm working my way through the open DBCP bugs with a view to getting the DBCP code (and the POOL code as some changes may be required there) into a state where it is ready for the first v2 release.
I've quickly reached DBCP-154 that requests that logging is added. This is not a new request and goes back to DBCP-4 and possibly earlier. From memory there are a number of open DBCP bugs that require some form of logging. There are also lots of places where DBCP logs directly to stdout or stderr. This quickly brings us to the point of having to decide which logging framework to use. This is largely the same debate we had for POOL [1] but with a few key differences: - there are many more places where logging is required - there are many more places where logging could be useful Because of the volume of logging, I don't believe the JMX approach used for POOL is viable for DBCP. Therefore, I intend to go ahead and add a dependency on Commons-Logging. Mark [1] http://markmail.org/message/zuufedzkfx62v5eq --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
