Re: [INTERFACES] Java, JDBC & CORBA (fwd)

At 16:26 +0200 on 30/11/98, Andrew R. Jackson wrote:

> First, let me preface my answer to say that the main reason I am
>subscribed to this list is to read Peter's, and occassionally others',
>answers, comments, etc about using JDBC with Postgres.
>
> To answer Peter's question, personally I would prefer two drivers, each
>separate. The reason for this is that I don't want a Makefile deciding
>which one (1) will be compiled and installed when I have two (2) different
>versions of Java on most of the systems I work on (most have 3 Javas,
>actually). I'd hate to be locked into using one driver version, and thus
>one Java version for Postgres stuff, because the Makefile only detected
>one of the Javas (which would be the 1.1.x one for now and some long time
>into the future). I want to choose. I want to be able to develop a Java
>1.1.x solution and a Java 1.2 solution, not either/or.
>
> Now, what really matters is good install instructions. If the
>instructions included ways to solve problems like the one above, then
>that's best and I don't care. Nothing beats good, copius, verbose, clear,
>well-maintained docs. :)

How about a Makefile which has the two (three?) drivers as separate target.
So, I can do a "make 1.1" "make 1.2". If we want to be sophisticated, make
the default tarket (i.e. "make" without args) detect the version of Java on
the current computer, and make the appropriate driver for it.

I just wonder if it's impossible for the driver to load the appropriate
classes dynamically, based on the value of the "java.version" System
property.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma