That will not work, you can't use wildcards for classpath. When you add a folder to the classpath, it's expected to be a folder containing classes exploded (complete with the folder path matching the package names); when you add individual jars to the classpath you must add each separately.
-Ron On Tue, Nov 30, 2010 at 7:47 AM, BeNdErR <bendertheoffender...@hotmail.com>wrote: > > > > Bryan Pendleton-3 wrote: > > > > I believe that the server will need to have derby.jar in its classpath. > > When > > you use the EmbeddedDriver, the Derby database libraries run inside of > > your > > application's JVM and so they need to be in your application's classpath. > > Here, > > the relevant application is the server, since it is the one making the > > JDBC calls. > > > > thanks, > > > > bryan > > > > > > java -classpath :/home/user/app/lib/*:/home/user/app/shared/ > > Do I have to change this? I thought I already set it up properly :\ as you > can see in the classpath there's the path to derby (inside the lib folder), > maybe the " * " part is wrong. You think i need to specify the complete > path > .../lib/derby.jar or using the "star" works? > > Thanks > > > -- > View this message in context: > http://old.nabble.com/Derby-%3A-No-suitable-driver-found-for-jdbc%3Aderby%3Adb-create%3Dtrue-tp30335341p30339246.html > Sent from the Apache Derby Users mailing list archive at Nabble.com. > >
