Using Derby DB in a java application

[CajunProgrammer]

I'm new to the forum. Please excuse any protocols I'm may not have followed in this post.

I have Netbeans 6.9.1 installed. I wrote an application that uses a derby database.

I can connect to the database and create tables and fields in the tables.

I can query the DB also.

However, when I try to access the DB from an application that I wrote, I get a "Driver not found" error when I use Class.forName("org.apache.derby.jdbc.ClientDriver").

[shortrun]

Did you set the class path in the operating system?

Here is an example I found by searching-

Windows class path:
C:\Derby\lib\derby.jar;C:\Derby\lib\derbytools.jar;C:\myPath\myDevDir

UNIX class path:
/Derby/lib/derby.jar:/Derby/lib/derbytools.jar:/myPath/myDevDir

I had a similar problems but not with Derby.
It was suggested I needed to set the Class path, which it did try.
I never did figure my problems out. So this is as far as I can go with helping you.

[CajunProgrammer]

Thank you for replying with your assistance.

Yes, I did try set the classpath. I also tried to set it from your suggestions just in case I did something wrong.

It still doesn't work.

I would have assumed everything would have been installed as it is bundled with netbeans.

I believe it is since I can execute commands on the database from the services tab.

I can only assume that the program cannot see the driver.

If it helps, here is a code snippet.

When the contructor is called, it errors to the ClassNotFoundException.

Again, thanks for assisting.

Code begins here:

package databasetester;

import java.awt.*;
import java.sql.*;
import java.util.*;
import javax.swing.*;

/**
*
* @author
*/
public class databaseMgr {

static final String JDBC_DRIVER = "org.apache.derby.jdbc.ClientDriver";
static final String DATABASE_URL = "jdbc:derby://localhost:1527/studentDB";

private Connection connection;
private Statement statement;

public databaseMgr () {

try {

Class.forName(JDBC_DRIVER);

connection = DriverManager.getConnection(DATABASE_URL);

statement = connection.createStatement();
}
catch (SQLException sqlException) {
JOptionPane.showMessageDialog (null, sqlException.getMessage(),
"Database Errors", JOptionPane.ERROR_MESSAGE);

System.exit(1);
}
catch (ClassNotFoundException classNotFound) {
JOptionPane.showMessageDialog( null, classNotFound.getMessage(),
"Driver Not Found", JOptionPane.ERROR_MESSAGE);

System.exit(1);
}

finally {

try{
statement.close();
connection.close();
} // end try

catch (SQLException sqlException) {
JOptionPane.showMessageDialog(null, sqlException.getMessage(), "Database Error",
JOptionPane.ERROR_MESSAGE);

System.exit(1);
} // end catch
} // end finally

} // end databaseMgr

[CajunProgrammer]

My installation of glassfish is located at C:\Program Files\glassfish-3.0.1\javadb\lib.

Therefore, I set my classpath as

C:\Program Files\glassfish-3.0.1\javadb\lib\derby.jar;C:\Program Files\glassfish-3.0.1\javadb\lib\derbyclient.jar.

This should account for both the server and the embedded drivers.

Are there any other drivers I need to set in my classpath?

Are there any other netbeans configurations I've missed?

All indications seem to point to a correct configuration. However, I continue to get that same error.

So frustrating.

[CajunProgrammer]

My installation of glassfish is located at C:\Program Files\glassfish-3.0.1\javadb\lib.

Therefore, I set my classpath as

C:\Program Files\glassfish-3.0.1\javadb\lib\derby.jar;C:\Program Files\glassfish-3.0.1\javadb\lib\derbyclient.jar.

This should account for both the server and the embedded drivers.

Are there any other drivers I need to set in my classpath?

Are there any other netbeans configurations I've missed?

All indications seem to point to a correct configuration. However, I continue to get that same error.

So frustrating.

[markwade]

On Mar 12, 2011, at 4:10 PM, CajunProgrammer wrote:

[CajunProgrammer]

Mark,

There were no Java DB libraries. However, there were glassfish libraries.

Well, that worked.

So, I thank you very much for your help.

It was very frustrating. But you resolved the issue for me.

Thanks again. I hope I can return the favor one day.

[markwade]

[markwade]

[markwade]

[CajunProgrammer]

I wasn't clear on my response.

All I added were the derby.jar and the derbyclient.jar. I think these would represent the embedded driver and the client server driver.

Yes, I'm all for keeping the application footprint small.

I was confused because I figured since netbeans has an embedded derby implementation (Glassfish), I didn't think I acutally needed to add any further libraries. However, I can see now that I am just adding the drivers to the application. I'm what you call an experienced novice with netbeans.

[markwade]

On Mar 14, 2011, at 8:30 PM, CajunProgrammer wrote: