db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmars...@Sourcery.Org>
Subject Re: MyEclipse and Derby - Best Practice question
Date Thu, 30 Sep 2004 16:32:10 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joachim Dagerot wrote:
> Hi everybody, my second post! :-)

> I don't really know what I want, but I would like an embedded DB
> (atleast in production) which I can access and edit both via my
> application and via DBE, if this means I should run the NetServer
> during development and embedded during production I'm find with that,
> but what is best practice, how is everyone else doing this?
>
>

One option is to set the derby.drda.startNetworkServer=true property in
your derby.properties file.  Your application can continue to use the
embedded driver and network server will start in the same JVM as soon as
cloudscape starts. You could then configure DBE to access using JCC.
This is a common configuration for applications that require primarily
embedded access but need occasional access from another JVM.  You just
need to make sure that your application has loaded cloudscape (thus
started network server) before you try to connect with the JCC driver.

Kathey




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBXDUKG0h36bFmkocRAmm3AKCsZHyoUKIMSpEWDJbQe0S8wBf7SACgs6U1
gt23N1lj0PDyZ3LPItHdl+c=
=le9P
-----END PGP SIGNATURE-----

Mime
View raw message