commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Graham <>
Subject RE: DBCP status?
Date Thu, 03 Jul 2003 01:24:11 GMT
--- "Noel J. Bergman" <> wrote:
> > > Some of the "AbandonedTrace" behavior is still necessary to
> implement
> > > the JDBC specification.  Connections still need to track outstanding
> > > statements and results sets, which are closed by Connection.close().
> > Agreed, but the way it was implemented was completely wrong.  The
> behavior
> > should not have been in a superclass and forced unrelated classes to
> > subclass it.
> I actually had a sentence about that, but I removed it.
> > Let DBCP focus on it's core responsibilities and provide easy
> > hooks to allow logging, policy decisions, etc.
> What hooks do you see as necessary in the base class(es)?

Listener and Strategy architectures are really useful for implementing
hooks that don't require subclassing.  I really think DBCP should use
commons-logging but if the majority believes otherwise, I'll make that
compromise.  For other features we may be able to leverage the
notifications that commons-pool already sends out and translate them into
DBCP events.

I'd like to see the next release of DBCP squash the open bugs and then we
can remove the deprecated Abandoned* classes and start on some new ideas. 
If they're significantly different than the current DBCP, we can increment
the major release number to 2.0 and break backwards compatibility to move


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

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

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

View raw message