1. You should import org.apache.derby.jdbc
2. There is -no- reason for you to hide your reference to derby if you
hard code the name. Just do new org.apache.derby.jdbc.EmbeddedDriver().
No need to muck around with dynamic class loading unless you get
the name of the driver from some configuration source.
3. Yes, I have successfully used derby.
Kind regards,
Peter Kriens
KF> Anybody get the derby bundle from
KF> orbit(http://www.eclipse.org/orbit/)
KF> working successfully? I not sure how I should use the Derby bundle.
KF> I'm trying to establish an embedded connection....
KF> public String driver = "org.apache.derby.jdbc.EmbeddedDriver";
KF> Class.forName(driver).newInstance();
KF> But it fails with....
KF> java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDriver
KF> You can't use "Class.forName" in an osgi bundle correct?
KF> So how should I should I create an embedded connection to a database
KF> with the derby bundle? I have read articles seeing people referring to
KF> it but never actually seen an example.
KF> Thanks for your help,
KF> Kevin
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
