Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 62321 invoked by uid 500); 17 Apr 2002 12:30:59 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 62310 invoked from network); 17 Apr 2002 12:30:59 -0000 From: "Carsten Ziegeler" To: Subject: RE: JDK 1.3 vs JDK 1.4 issue Date: Wed, 17 Apr 2002 14:33:14 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <028001c1e60a$d95ee1a0$9274558b@vgritsenkopc> X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 17.04.2002 14:30:57, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 17.04.2002 14:30:59, Serialize complete at 17.04.2002 14:30:59 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Vadim Gritsenko wrote: > ... > > I don't think so. See EsqlConnection: > > ----------------- > @JDBC3_START@ > public void setHoldability(int holdability) > throws SQLException > { > connection.setHoldability(holdability); > } > ----------------- > > When compiled with JDK1.4, and used on JDK1.3, connection.setHoldability > would not be found and class (EsqlConnection) would not be loaded. > Why do you think so? I thought that as long as setHoldability is not called I don't get any problems with this. And it shouldn't be called with 1.3 as it does not belong to the Connection interface. Or am I wrong here? Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org