Hi Mamta thanks for the answer.
So basically Derby will only be up in one JVM at a
If a tool like ij is started in a new JVM, then it will not be able to
connect to an embedded database which has been started by a different JVM.
On 9/10/07, Néstor
Thanks for the answer.
So this means that if I open the
database using the EmbeddedDriver driver no
one can access the database
from an outside connection?. Includiing tools
De: Kristian.Waagan@Sun.COM [mailto:Kristian.Waagan@Sun.COM]
el: Monday, September 10, 2007 4:27 AM
Para: Derby Discussion
Re: How to restrict external connections
Néstor Boscán wrote:
> Is there a way to restrict external connection to a Derby
> only want the JVM to be able to connect to the Derby
database and no
> other external processes.
I have misunderstood, sounds like you simply want to use Derby
This is done by using org.apache.derby.jdbc.EmbeddedDriver and
the connection URL as 'jdbc:derby:myDatabase[;create=true;...]'.
default, no network server will be started and only the JVM is able
access the database.
Note that 'myDatabase' can point to a
database by using either a relative
path (relative to derby.system.home ,
or current working directory if it is
unset) or an absolute
Did that answer you question, or do you have any further