Fwd: Problems with drivers for Java DB (Derby)

The problem occurred because I did not remember to put the Derby jar files in  /Libary/Java/Extensions.

After doing that the SimpleApp worked as intended from xcode.

Thanks to Michael Louka for figuring that out.

I tried to follow the Derby manual on setting the CLASSPATH as if the Mac was a UNIX machine. That made SimpleApp work

from the command line by either running the SimpleApp.class that came with the Derby release or a similar .class file generated by xcode.

 It did not work when trying to run SimpleApp.jar from xcode.

I guess an Apple release of Java DB only have to install the Derby Jar files in  /Libary/Java/Extensions

as part of the Java install.

Thank you!

Kolbjørn

On Sep 27, 2006, at 5:53 AM, Jim Davidson wrote:

On 9/26/06 12:03 PM, Kolbjørn Aambø <email@hidden> wrote:

Subject: Problems with drivers for Java DB (Derby)

From: Kolbjørn Aambø <email@hidden>

Date: Tue, 26 Sep 2006 08:47:04 +0200

To: Java-Dev <email@hidden>

 I downloaded JavaDB from SUN for LINUX and tried it with XCode and Java 1.5 for Mac OS X 10.4.7 on a PowerBook G4 but got the following (Below) that I am unable to cope with on the Mac. There seem to be a IBM driver that is lacking and no way to get that to work for the Mac.

Java DB is "Sun's supported distribution of the Apache Derby 100% Java technology open source database".  In core areas, I don't believe that it differs from Derby at all.  IBM does something similar with Cloudscape and Derby.

You're right, there's no Java DB for the Mac. OTOH, as another poster points out, there's a version of Derby for the Mac, which I use extensively, and which seems to work fine.

It was things like this that I was hoping Apple Computers to address in

Java 1.6 now that Java DB is claimed by SUN to be a integral part of Java

2 SE version 6.

Java SE 6 isn't shipping yet.  Once Sun ships the official version, and Apple does likewise, I'm sure that they will offer appropriate support.  As I say, Derby works fine now, so it's not a big jump.

By the way I have seen a analogous problem with mySQL too.

I haven't.  I previously used MySQL Connector/J 3.1.12, with no problem. We're in process of switching to 5.0.3, but again it seems to behave OK.

It seems like

it is easier to connect a camera to a mac than to get a relational database to work from Java.  The difference is probably that Apple is

doing a job with USB-drivers. Apple do not seem to do the same job with JDBC drivers. I hope that will change or that database implementers at least make drivers available, for the Mac. If the jdbc drivers are not easily available the point of the rest of the database seem to be of academic value only.

There are lots of drivers that work on the Mac.  Note that Type 4 drivers are all Java, so most of them Just Work on the Mac with minimal work.

Since the other vendors for Java DB (IBM, SUN, Apache) do not address Mac OS X in particular there seem to be at least implicit hints that the jdbc-drivers for Java DB is Apples responsibility.

See above.  Only Sun produces Java DB.  Apache and IBM use different names for the same project.

-Jim

_______________________________________________

Do not post admin requests to the list. They will be ignored.

Java-dev mailing list      (email@hidden)

Help/Unsubscribe/Update your Subscription:

http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden