Note that it's possible for application A to startup the network server
in a separate thread. That is, application A and the network server
could run in the same VM. In this scenario, Ole gets what he wants. For
more information on this, please see the section titled "Starting the
Network Server from a Java application" in the Derby Admin Guide:
http://db.apache.org/derby/docs/10.4/adminguide/
Hope this helps,
-Rick
Ole Ersoy wrote:
Hi Michael,
Thanks for the clarification. That answers my question.
Thanks again,
- Ole
[EMAIL PROTECTED] wrote:
-----Original Message-----
From: Ole Ersoy [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 8:29 AM
To: [email protected]
Subject: Embedded and Network Simultaneous Connections
Hi,
I was wondering if it's possible for a network client to connect to a
derby instance running in embedded mode. So in other words client A is
running embedded derby, and (client B - Separate JVM) wants to
connect to
it using the network driver.
Thanks,
- Ole
I don't think your question make sense.
If you're running Derby in embedded mode, then you don't have a
"client",
you have an application which has a derby database embedded in it.
So I think your question becomes "Application A has derby embedded in
it. A
separate application B, on a different JVM, would like to connect to the
Derby instance running in A."
Since you specified that the instance of Derby is embedded there is no
network service started and thus you can't connect to that instance
of Derby
unless you write your own service as part of application A.
