You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Greg Martin <gr...@telusplanet.net> on 2009/10/11 02:10:28 UTC
Derby plugin class sometimes not found exception
Class.forName("org.apache.derby.jdbc.EmbeddedDriver") when called from
within an Eclipse view class throws class not found however from a main in
the same class it succeeds and I can get a connection o the db. I can
connect to the db from ij fine as well. Derby version is 10.5.3 and eclipse
is 3.5.1. Any help would be appreciated.
Regards,
Greg Martin
http://www.gregmartin.name/
RE: Derby plugin class sometimes not found exception
Posted by Greg Martin <gr...@telusplanet.net>.
I'm using the derby plugin which sets the classpath up for the project. It
may have something to do with the way the views are instantiated though but
if that is the case I would expect this to be a common problem with users of
the plugin. I will try the eclipse lists.
- Greg
http://www.gregmartin.name/
-----Original Message-----
From: Dag.Wanvik@Sun.COM [mailto:Dag.Wanvik@Sun.COM]
Sent: Saturday, October 10, 2009 9:16 PM
To: Derby Discussion
Subject: Re: Derby plugin class sometimes not found exception
Greg Martin <gr...@telusplanet.net> writes:
> Class.forName("org.apache.derby.jdbc.EmbeddedDriver") when called from
> within an Eclipse view class throws class not found however from a main in
> the same class it succeeds and I can get a connection o the db. I can
> connect to the db from ij fine as well. Derby version is 10.5.3 and
eclipse
> is 3.5.1. Any help would be appreciated.
I don't use Eclipse, but this sounds like a classpath problem. Maybe
some Eclipse experts can help you, I don't believe this is a Derby
issue.
Dag
Re: Derby plugin class sometimes not found exception
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Greg Martin <gr...@telusplanet.net> writes:
> Class.forName("org.apache.derby.jdbc.EmbeddedDriver") when called from
> within an Eclipse view class throws class not found however from a main in
> the same class it succeeds and I can get a connection o the db. I can
> connect to the db from ij fine as well. Derby version is 10.5.3 and eclipse
> is 3.5.1. Any help would be appreciated.
I don't use Eclipse, but this sounds like a classpath problem. Maybe
some Eclipse experts can help you, I don't believe this is a Derby
issue.
Dag