Exported Jar file throws exception (JDBC)

Question

I have made use of JDBC in one of my projects and it worked flawlessly in Eclipse. I had to add the ojdbc6.jar to Java Build Path to the project BTW. (I have also not included any Class.forName statements in the code since I heard it's optional for JDBC 4 and above)

When I export the project into a jar file, and try to run it, it complains saying "No driver found for JDBC" and so on. I can see that this is because the ojdbc6.jar is missing from the build path now. Can someone please let me know of a solution?

Thanks!

related https://stackoverflow.com/q/18413014/85421 ? – user85421 Sep 24 '18 at 12:07 — user85421, Sep 24 '18 at 12:07

score 1 · Answer 1 · answered Nov 19 '13 at 01:21

Here is a simple method to export a JAR that uses external jar as libs:

You have to write a manifest file, I named it jar.manifest.
The content in manifest file looks like:

Manifest-Version:1.0
Main-Class:com.enginebai.activity.MyJDBCProgram
Class-Path:lib/ojdbc6.jar lib/some-externam-lib.jar

and make sure to put a blank line under Class-Path, otherwise the JAR won't run. (I have no idea why to put a blank line over there.)

Let's go back to eclipse:

In eclipse, you export your classes and remember to select above manifest file.
Make sure your ojdbc6.jar be in project/lib folder.
Open your terminal and cd to project root directory, enter `java -jar your-jar-name.jar', it should work then.

score 0 · Answer 2 · answered Nov 18 '13 at 22:06

0

put ojdbc6.jar on classpath when you run your jar

answered Nov 18 '13 at 22:06

Alien11689

461
4
5

Can you tell me how to do that since java -cp accepts only the class Name and all I have is only the JAR? – Sasanka Panguluri Nov 18 '13 at 22:07
On linux java -cp ojdbc.jar:your.jar -jar YourMainClass – Alien11689 Nov 18 '13 at 22:09
File ojdbc6.jar must be in your working directory. and you should have everything defined in cp: java -cp ojdbc6.jar:myJar.jar:. YourMainClass – Alien11689 Nov 18 '13 at 22:22

score 0 · Answer 3 · answered Nov 18 '13 at 22:31

I have done some research and found a solution that seems to work. I have exported the project into a "Runnable Jar file" instead of just a "jar file". This way, I was actually able to repack Jar files from my Build Path into the new Jar file I am exporting my project to. Simple and clean.

You also might want to look at signed Jar files and any other certificates in your existing jar files in the Build Path. They cannot directly be repacked through the export option.

Exported Jar file throws exception (JDBC)

3 Answers3