got it! Looks like my Eclipse references a derby.jar (whatever plugin) which causes problems when I explicitly reference another derby.jar... http://www.mail-archive.com/[email protected]/msg05999.html
> -----Original Message----- > From: Clemens Wyss [mailto:[email protected]] > Sent: Thursday, September 30, 2010 9:26 PM > To: 'Derby Discussion' > Subject: RE: instantiating EmbeddedDriver -> FileNotFoundException > > > I am running the my app from within Eclipse hence I doubt its > a typo... > > > -----Original Message----- > > From: Donald McLean [mailto:[email protected]] > > Sent: Thursday, September 30, 2010 8:44 PM > > To: Derby Discussion > > Subject: Re: instantiating EmbeddedDriver -> FileNotFoundException > > > > > > I'm guessing that it's something really aggravating like a > typo in the > > classpath. > > > > Donald > > > > On Thu, Sep 30, 2010 at 2:25 PM, Clemens Wyss > > <[email protected]> wrote: > > > Hi all, > > > when I try to instantiate the EmbeddedDriver: > > > ... > > > org.apache.derby.jdbc.EmbeddedDriver driver = > > > (EmbeddedDriver) > > Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance(); > > > ... > > > I get a FileNotFoundException, unfortunately the missing > > file is not mentioned: > > > > > >> Thread [main] (Suspended (exception FileNotFoundException)) > > >
