Any way to prevent Derby from writing temp directory?
843859Nov 9 2007 — edited Nov 20 2014I'm trying to put together a web start application that contains a small read-only derby (Java DB) database. I have crossed the first web start hurdle in that the Derby Developer's Guide provides instructions for bundling a read-only database inside a jar file. However, it appears that derby needs to be able to write a temp directory during operation. I'd really like to avoid requiring the user to give file-permissions, so I am currently at an impasse.
My question: does anyone know if it is possible to disable the need to write to a temp directory, or some other way to get around this problem?
Thanks!