commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <>
Subject Re: Replace System.out, System.err and printStackTrace() with Commons Logging?
Date Tue, 20 Apr 2004 20:08:55 GMT
Generating DBCPEvents is the way to go.
No direct dependency on any logging library please.
The DBCP core should be able to run on a standard tomcat with no extra 
  logging requirments.

-- Dirk

Alex Karasulu wrote:

> Steve,
> Forgot to mention another added benefit of using a monitor (callback)
> interface is that you don't need a commons-logging dependency.
> If you define a DBCPMonitor interface to announce notable events 
> you can leave the decision to have a dependency on logging up to the 
> user of the API.  So DBCP does not need a commons-logging dependency.
> You might stuff a Null monitor that does nothing into DBCP at first
> and allow others to be set by the user.  Users can implement 
> a logging version of the monitor interface that uses commons-logging.
> Alex

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message