Re: Question : Can I use jdk1.2 for Oracle 8i

From: <Chris.M.Hawkins_at_HealthPartners.com>
Date: 1999/03/02
Message-ID: <7bh8c2$5m3$1_at_nnrp1.dejanews.com>#1/1


Peter,

Cris J. Holdorph noted:

> If you use any JDBC 2.x or Oracle specific
> methods/classes, your code will probably not work. e.g., You can not use
> OracleTypes.Cursor, or OracleCallableStatement. Because you can not compile
> with the Oracle classes, because the classes don't even match the JDBC 2.x
> interface signatures (let alone support JDBC 2.x).

I am not using Oracle extensions in my code. Nor am I having any problems with compilation. The problem I am having occurs at runtime. When, under JDK1.2 I run:

Class.forName("oracle.jdbc.driver.OracleDriver");

I get a ClassNotFoundException. It works fine under JDK1.1.7

Can anybody shed some light on what I can do differently to make this work for me under JDK1.2??

> You most definitely *can* use the Oracle Type 4 (thin) driver with
> JDK1.2. I am using it every day, as are many other people in my
> organisation.
>
> I do not, however, use any Oracle-specific extensions but check my
> code against other database engines by swapping out the driver and
> URL. If you're using Oracle specific extensions, well........what can
> I say? Your portability is nil without a rewrite and things break, as
> you have found.
>
> Please don't say that you need the extensions - been there, done that,
> heard it all before. NOT needing extensions is why we use Java instead
> of C or C++ with embedded SQL.
>
> Bottom line: the thin drivers work with JDK1.2. It's time to look at
> what bits of your code that use these drivers don't.
>
> Peter Wiley
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Tue Mar 02 1999 - 00:00:00 CET

Original text of this message