Then it's back to square one - my first advice. Derby classes are not
the part of the exported jar, so when you run your app you have to
point java to their actual location, i.e. fix this command line to
reflect your environment:
java -cp derby.jar;DerbySample.jar pkgEclipseDerby.frmDataDBSample
Andrus
On Jan 14, 2006, at 9:20 PM, David Costelloe wrote:
Hi Andrus,
Every runs ok within the Eclipse. Once I generate the export jar.
The application (GUI) loads as expected. The only issue being the
Derby connection.
Checked the Build Path and Derby.jar is there.
Thanks
Andrus Adamchik wrote:
Hmm... I didn't realize you are using a Derby Eclipse plugin. I
don't have any experience with the plugin. But from your earlier
message I take you are running from command line outside Eclipse?
So try running it inside Eclipse and see what happens. To do that
right click on your main class and do "Run As -> Java Application".
If this still doesn't work, here is an idea of a "brute force"
solution (those who know the plugin, may have a better one) -
ignore the plugin and add derby.jar to your project directly
(right click on your project folder, go to "Preferences -> Java
Build Path -> Libraries" and select a path to derby.jar.
Andrus
