So you are setting derby.system.home in your jnlp properties to point to a url? If not, what is derby.system.home pointing to? I have also deployed derby very successfully from within webstart, however the database was on the local filesystem.
-Alan Baldwin- -----Original Message----- From: Ole-H [mailto:[EMAIL PROTECTED] Sent: Friday, December 01, 2006 2:50 AM To: [email protected] Subject: Derby in webstart Hi I have an application that uses derby for storing data to a remote database, but stores the data localy if the remote server is unavailable. This works fine when i run it as an normal java application, but when i run it from it from webstart and the server is offline, things get very slow. It seems derby is trying to make connections to the url specified in the codebase in the jnlp file. Does anyone know how to fix this? Any help appreciated. -- View this message in context: http://www.nabble.com/Derby-in-webstart-tf2736794.html#a7635375 Sent from the Apache Derby Users mailing list archive at Nabble.com. --------------------------------------------------------------------------------------------------------- This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. ---------------------------------------------------------------------------------------------------------
