Oracle Driver / JAR problem

Question

Hi,
Here is the troublesome code.....
public void connect()throws Exception{
          //set up the Driver
          try     {     
               //Problem here when running in a JAR
               DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
               JOptionPane.showMessageDialog(null, "Conencted to database!", "Connected",JOptionPane.ERROR_MESSAGE);
          catch(Exception e){
               System.out.println("Driver initialisation failed");
               JOptionPane.showMessageDialog(null, "Unable to locate OracleDriver()", "Error in connection",JOptionPane.ERROR_MESSAGE);
          //Make a connection to the database     
          try {
               theConnection = DriverManager.getConnection(c.getDbUrl(), c.getUserName(), c.getPassword());
          catch(Exception e) {
               System.out.println("failed to make a connection");
               JOptionPane.showMessageDialog(null, "Problem in connection. Please check database connection settings and re-try.", "Error in connection",JOptionPane.ERROR_MESSAGE);
     }This code works fine when running via Eclipse, but, when I put it into an executatble JAR, it fails. I know it fails at the line DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver()); (as you can see in the code above)
Any ideas?
liktid

Answer 1

I replaced
DriverManager.registerDriver (new
oracle.jdbc.driver.OracleDriver());with
Driver driver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver
").newInstance();
DriverManager.registerDriver( (java.sql.Driver)
er) driver);now an error gets caught on EVERY occasion (as seen
in the code in the first post), even in eclipse. The
previous version was ok. any further suggestions?
litkidNone of that stuff is necessary. This is sufficient:
Class.forName("oracle.jdbc.driver.OracleDriver");This works in production for me.
Your problem is that your executable JAR manifest Class-Path doesn't include the ojdbc14.jar OR that JAR isn't where your Class-Path says it should be relative to your executable JAR.
%