Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of brett.porter@gmail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=hwrUJqtfPHhirGp+PcYBMwmtVn8YffPVdz1q6emiIajEcfNBzY+76gZ7BckvHreYhpwarMJU0oStV/FZEfxDdXaZQX0frCiB/FXSp4QjCvkRpxj7hZRi4dKvuQTgzakhLfeRVBaGa9sfqlR6m42mZzk9m+LUHGyQxRDOJwci+gc=
Message-ID: <9e3862d80607312033y7d1ab0c1p372b07d1d058f46f@mail.gmail.com>
Date: Tue, 1 Aug 2006 13:33:07 +1000
From: "Brett Porter" <brett.porter@gmail.com>
To: open-jpa-dev@incubator.apache.org
Subject: Re: JDBC 4 (was: Was it just me?)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 01/08/06, Patrick Linskey <plinskey@bea.com> wrote:
> Sweet! I think that that will make you the first non-BEA employee
> committing to the codebase.

:)

>
> > BTW, you may be aware, but it doesn't compile on Java 6 due
> > to the JDBC interface changes. I'll add that to JIRA if its
> > not there already.
>
> Yeah, we've had this problem in the past as well. Historically, we've
> created special modified JDBC jars so that we can compile on earlier VM
> versions. How is this type of problem typically handled in Apache-land?

Isn't this the other way around? If the additional methods are
implemented to make it compile on Java 6, it will continue to be
binary compatible with the earlier JDBC versions.

Cheers,
Brett