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 Alberto Molpeceres <al...@gmail.com> on 2006/05/29 13:15:05 UTC
problem with embeded derby database and javawebstart
Hi all,
This is my first mail to the list, so, I want to say hello to all
members. Greetings from Spain :-D.
Well, we are working in a Java Web Start application that use a
database as source of information. Till now he have do our
test&deploy in intranet enviroments, so we used a central postgres
database.
Now we have to write a internet version of our application using an
embeded database for read only data. We are trying to use derby
embeded with this database compressed in a jar file, but we are not
very lucky till now, the console reports that the database can't be
found :-(.
Database's jar is referenced in the JNLP file, and it's in the same
place as all other jars, so it shouldn't be a problem, still we
receive a:
SQL Exception: Failed to start database 'jar:(database.jar)/testDB',
see the next exception for details.
...
Java exception: 'No such file or directory: java.util.zip.ZipException'.
java.util.zip.ZipException: No such file or directory
Our relevant connection information is:
databaseDriverName = "org.apache.derby.jdbc.EmbeddedDriver";
connectionURL = "jdbc:derby:jar:(database.jar)/testDB";
This database works fine using it as a desktop application and
referenced from it's folder in the URL, and the JWS application has
all permissions.
Any idea?. Are we missing something in the URL?. Can't a derby
database be loaded from a jar in a Java web start application?.
Thank you very much for you attention,
al.
Re: problem with embeded derby database and javawebstart
Posted by Alberto Molpeceres <al...@gmail.com>.
Ups. I didn't read the key word "absolute" :-(.
al.
On 5/30/06, David Van Couvering <Da...@sun.com> wrote:
> Looking at the docs
>
> http://db.apache.org/derby/docs/dev/devguide/cdevdeploy11201.html#cdevdeploy11201
>
> it says the path to the archive containing the database must be an
> *absolute path*. This of course may be a problem when you're loading on
> a remote machine. Does anyone have any tips on how to manage this?
>
> David
>
> Alberto Molpeceres wrote:
> > Hi all,
> >
> > This is my first mail to the list, so, I want to say hello to all
> > members. Greetings from Spain :-D.
> >
> > Well, we are working in a Java Web Start application that use a
> > database as source of information. Till now he have do our
> > test&deploy in intranet enviroments, so we used a central postgres
> > database.
> >
> > Now we have to write a internet version of our application using an
> > embeded database for read only data. We are trying to use derby
> > embeded with this database compressed in a jar file, but we are not
> > very lucky till now, the console reports that the database can't be
> > found :-(.
> >
> > Database's jar is referenced in the JNLP file, and it's in the same
> > place as all other jars, so it shouldn't be a problem, still we
> > receive a:
> >
> > SQL Exception: Failed to start database 'jar:(database.jar)/testDB',
> > see the next exception for details.
> > ...
> > Java exception: 'No such file or directory: java.util.zip.ZipException'.
> > java.util.zip.ZipException: No such file or directory
> >
> > Our relevant connection information is:
> >
> > databaseDriverName = "org.apache.derby.jdbc.EmbeddedDriver";
> > connectionURL = "jdbc:derby:jar:(database.jar)/testDB";
> >
> > This database works fine using it as a desktop application and
> > referenced from it's folder in the URL, and the JWS application has
> > all permissions.
> >
> > Any idea?. Are we missing something in the URL?. Can't a derby
> > database be loaded from a jar in a Java web start application?.
> >
> > Thank you very much for you attention,
> >
> > al.
>
Re: problem with embeded derby database and javawebstart
Posted by Andreas Korneliussen <An...@Sun.COM>.
David Van Couvering wrote:
> Looking at the docs
>
> http://db.apache.org/derby/docs/dev/devguide/cdevdeploy11201.html#cdevdeploy11201
>
>
> it says the path to the archive containing the database must be an
> *absolute path*. This of course may be a problem when you're loading on
> a remote machine. Does anyone have any tips on how to manage this?
>
If possible, put the jar file in the class path, and connect using
"jdbc:derby:classpath:/databasePathWithinArchive"
http://db.apache.org/derby/docs/dev/devguide/tdevdeploy39856.html
Andreas
> David
>
> Alberto Molpeceres wrote:
>> Hi all,
>>
>> This is my first mail to the list, so, I want to say hello to all
>> members. Greetings from Spain :-D.
>>
>> Well, we are working in a Java Web Start application that use a
>> database as source of information. Till now he have do our
>> test&deploy in intranet enviroments, so we used a central postgres
>> database.
>>
>> Now we have to write a internet version of our application using an
>> embeded database for read only data. We are trying to use derby
>> embeded with this database compressed in a jar file, but we are not
>> very lucky till now, the console reports that the database can't be
>> found :-(.
>>
>> Database's jar is referenced in the JNLP file, and it's in the same
>> place as all other jars, so it shouldn't be a problem, still we
>> receive a:
>>
>> SQL Exception: Failed to start database 'jar:(database.jar)/testDB',
>> see the next exception for details.
>> ...
>> Java exception: 'No such file or directory: java.util.zip.ZipException'.
>> java.util.zip.ZipException: No such file or directory
>>
>> Our relevant connection information is:
>>
>> databaseDriverName = "org.apache.derby.jdbc.EmbeddedDriver";
>> connectionURL = "jdbc:derby:jar:(database.jar)/testDB";
>>
>> This database works fine using it as a desktop application and
>> referenced from it's folder in the URL, and the JWS application has
>> all permissions.
>>
>> Any idea?. Are we missing something in the URL?. Can't a derby
>> database be loaded from a jar in a Java web start application?.
>>
>> Thank you very much for you attention,
>>
>> al.
Re: problem with embeded derby database and javawebstart
Posted by David Van Couvering <Da...@Sun.COM>.
Looking at the docs
http://db.apache.org/derby/docs/dev/devguide/cdevdeploy11201.html#cdevdeploy11201
it says the path to the archive containing the database must be an
*absolute path*. This of course may be a problem when you're loading on
a remote machine. Does anyone have any tips on how to manage this?
David
Alberto Molpeceres wrote:
> Hi all,
>
> This is my first mail to the list, so, I want to say hello to all
> members. Greetings from Spain :-D.
>
> Well, we are working in a Java Web Start application that use a
> database as source of information. Till now he have do our
> test&deploy in intranet enviroments, so we used a central postgres
> database.
>
> Now we have to write a internet version of our application using an
> embeded database for read only data. We are trying to use derby
> embeded with this database compressed in a jar file, but we are not
> very lucky till now, the console reports that the database can't be
> found :-(.
>
> Database's jar is referenced in the JNLP file, and it's in the same
> place as all other jars, so it shouldn't be a problem, still we
> receive a:
>
> SQL Exception: Failed to start database 'jar:(database.jar)/testDB',
> see the next exception for details.
> ...
> Java exception: 'No such file or directory: java.util.zip.ZipException'.
> java.util.zip.ZipException: No such file or directory
>
> Our relevant connection information is:
>
> databaseDriverName = "org.apache.derby.jdbc.EmbeddedDriver";
> connectionURL = "jdbc:derby:jar:(database.jar)/testDB";
>
> This database works fine using it as a desktop application and
> referenced from it's folder in the URL, and the JWS application has
> all permissions.
>
> Any idea?. Are we missing something in the URL?. Can't a derby
> database be loaded from a jar in a Java web start application?.
>
> Thank you very much for you attention,
>
> al.