Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 91908 invoked from network); 29 May 2006 11:15:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 May 2006 11:15:32 -0000 Received: (qmail 14217 invoked by uid 500); 29 May 2006 11:15:31 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 13851 invoked by uid 500); 29 May 2006 11:15:30 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 13840 invoked by uid 99); 29 May 2006 11:15:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 May 2006 04:15:30 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of alberto.molpeceres@gmail.com designates 66.249.82.193 as permitted sender) Received: from [66.249.82.193] (HELO wx-out-0102.google.com) (66.249.82.193) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 May 2006 04:15:29 -0700 Received: by wx-out-0102.google.com with SMTP id i31so118319wxd for ; Mon, 29 May 2006 04:15:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=qc60m/P22yr6YujOVPyMdWNjmlWW0iE6gUJO7RR/qq+HKQBjoPxaNG6rMxRQvTy/GBNUqMdm8/Y146+ly4q8CoIr7alfatLoqzTucwkkgAHrRmCZfJrHGroT/U9O7HRgLVFZ9j3f+woZnORPTAqcSi6/5qNjgH5Gg4rnb7uZZaw= Received: by 10.70.113.17 with SMTP id l17mr2205230wxc; Mon, 29 May 2006 04:15:05 -0700 (PDT) Received: by 10.70.22.9 with HTTP; Mon, 29 May 2006 04:15:05 -0700 (PDT) Message-ID: <7338a19f0605290415v72a0136te90001557b792f73@mail.gmail.com> Date: Mon, 29 May 2006 13:15:05 +0200 From: "Alberto Molpeceres" To: derby-user@db.apache.org Subject: problem with embeded derby database and javawebstart MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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 =3D "org.apache.derby.jdbc.EmbeddedDriver"; connectionURL =3D "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.