commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <craig...@apache.org>
Subject Re: commons dbcp or pool problems
Date Wed, 27 Feb 2002 16:45:19 GMT


On Wed, 27 Feb 2002, Juozas Baliuka wrote:

> Date: Wed, 27 Feb 2002 09:27:20 +0100
> From: Juozas Baliuka <baliuka@mwm.lt>
> Reply-To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
> Cc: aaron.smuts3@verizon.net
> Subject: Re: commons dbcp or pool problems
>
>
> <skip>
> > > > Craig
> > > I see only one possible solution : to have two tagets in ant script, one
> for
> > > jdk1.3 and for 1.4,
> > > conditional compling  is not very nice solution, but I see no choises.
> > >
> >
> > Doing the conditional compilation part is pretty straightforward.  We'll
> > also want to make the DBCP runtimes smart about which implementation class
> > it uses for Connections based on what JVM the application is running in,
> > without requiring the application itself to configure things any
> > differently.
> >
> > Also, whoever builds a DBCP distribution bundle needs to make sure they
> > run both compilers, so that both implementation classes are available in
> > the JAR file ...
> >
> > Craig
>  It is very trivial to implement Connection interface at runtime, but some
> performance can be lost.
> ( see java.reflect.Proxy )
>

That only works if we're willing to make 1.3 the base platform.
Historically, most commons packages specify 1.2 (although some
deliberately maintain support for 1.1 as well).

Craig


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message