According to the documentation, with Derby we can deploy applets with read-only databases packed as a jar file.
However, Derby creates temporary files for complex queries, such as SELECT DISTINCT:
Is it possible to use a derby database (packed in a jar file) from an applet, without having Derby creating any temporary file?
(and so, no need to have signed applets. so, no need to ask the user to trust the applet)
This topic has been locked.
1 reply Latest Post - 2007-03-19T23:17:53Z by Stan
Pinned topic Derby, Applets and temporary files
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2007-03-19T23:17:53Z at 2007-03-19T23:17:53Z by Stan
Stan 120000HAGM267 PostsACCEPTED ANSWER
Re: Derby, Applets and temporary files2007-03-19T23:17:53Z in response to dportabellaThere is not a way to tell Derby not to use temporary files. You can set the location of the files setting derby.storage.tempDirectory but this will still require write permissions for the applet. Have you considered handling your persistant storage needs by using servlets? This will avoid the many restrictions placed on applet processing.