Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: Correct Derby software ?
From: Tim Watts <tim@cliftonfarm.org>
To: Derby Discussion <derby-user@db.apache.org>
In-Reply-To: <1340284916.30268.1260.camel@dellberry>
References: 
	 <9FA7F6B8122B1143A124094C0234D788018916D7@serveur-mails.sela-light.com>
	 <1340284916.30268.1260.camel@dellberry>
Content-Type: multipart/signed; micalg="pgp-sha1";
 protocol="application/pgp-signature"; boundary="=-BaEMD57OAckCD2ryAI+Q"
Organization: Clifton Farm
Date: Thu, 21 Jun 2012 09:31:01 -0400
Message-ID: <1340285461.30268.1266.camel@dellberry>
Mime-Version: 1.0


--=-BaEMD57OAckCD2ryAI+Q
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 2012-06-21 at 09:21 -0400, Tim Watts wrote:
> On Thu, 2012-06-21 at 13:54 +0200, Isabelle DASTUGUE wrote:
> > Hello,
> >=20
> > I have a Derby database that works when I start it from Eclipse, but
> > when I try to run it from the. Jar of my application, it does not
> > work.
> >=20
> > Here are two successive errors:
> > java.sql.SQLException: Failed to start database 'C:\Test\Base' with
> > class loader sun.misc.Launcher$AppClassLoader@35ce36, see the next
> > exception for details.
> > then
> > Caused by: java.sql.SQLException: Startup failed due to missing
> > functionality for org.apache.derby.iapi.store.access.AccessFactory.
> > Please ensure your classpath includes the correct Derby software.
> >=20
> > I put the Derby access to my files in the classpath in environment
> > variables, but it's still not working.
> >=20
> > My four files:
> > - Derby.jar,
> > - Derbyclient.jar,
> > - Derbynet.jar,
> > - Derbytools.jar.
> > Are exactly the same and on the same PC ...
> >=20
> > Without the call to the base, my. Jar works.
> > With the base, I create the server, do I start Derby, I run the
> > instance but I cannot connect to the database at the address returned
> > is obviously good ...
> >=20
> > Any idea?
> >=20
> Check if there is a Class-Path entry in your jar's META-INF/MANIFEST.MF
> file.  If there is, then the dependent jars need to be specified there
> (space separated).  The jar locations must be specified relative to
> my.jar (IMPORTANT!).  So if my.jar and derbyclient.jar in the same dir
> then the entry should look like this:
>=20
>         Class-Path: derbyclient.jar
>=20
> But if my.jar is in base/ and derbyclient.jar is in home/libs then this:

TYPO:  meant base/libs not home/libs

>=20
>         Class-Path: libs/derbyclient.jar
>=20
> and base/ needs to be in CLASSPATH (so that my.jar will be found).
>=20
> See: http://docs.oracle.com/javase/6/docs/technotes/guides/jar/jar.html
> for all details on jars and manifests.
>=20
> (btw, if your app is using derby in client mode then I don't think you
> need all those jars, just derbyclient.jar).
>=20
> > Cordially
> >=20
> > Isabelle DASTUGUE
> >=20
>=20


--=-BaEMD57OAckCD2ryAI+Q
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAABAgAGBQJP4yIVAAoJEAfDBXDHBQilKVIH/0xm2iCDpZ0V0ll7J+h/piGI
rUoQmEfZn5L5uqBbbcgQuJvQp1+BywXVAaGsFxrP0MpLcsk1cDcL/sHfRemhIQrQ
FwkH7Ngh0BWyCpml23S1Yg3Tg1Fxe1/ofnXwz8XCbRTQ/YxsliEfgi+IwcmqmTyD
i8htum7TiTymQwW5EVVGrMqU/LSg5zNuuoXcOhr34WHHNAuNHd7xM6dRLQ7X5i/A
qZlVr7xHuf/UhHgExScWbuW9DMdHWpSO7O2O3Rqh08DVXfYbQCWtyCx0pPds9aYa
UEiI1Pdj6woq2t2r67+G2eB+YzYPpYCNyxsmdvSqP4vbtK2tDsHSkn7+Vw00U+k=
=zb5h
-----END PGP SIGNATURE-----

--=-BaEMD57OAckCD2ryAI+Q--