there?
A Derby database can be accessed from a CLASSPATH or jar file, but as read-only. Please
refer the following for more info:
http://db.apache.org/derby/docs/10.1/devguide/cdevdvlp19700.html
Regards,
Rajesh
On 1/17/06, David Costelloe <[EMAIL PROTECTED]> wrote:
Seems I have found the problem in my export.
1. Derby Jars are not being exported (only with Fat jar can I get this
to work)
2. Derby embedded database is not being found in the jar (it does exist)
by the application when it runs.
Seem once I move the jar from where it was built it can't find the
embedded database so it re-creates the database.
More problem now is if I include the db folders in the jar derby can't
find the database.
Is there a way I package the database in the jar and have it loaded from
there?
Seems to me to be not a good way seeing as embedded is not actually
embedded?
This is confusing to me but i did notice that once I moved the jar and
ran it in another directory the database directory was re-created only
without my tables and etc. The jar does contain the database folders as
below:
I'll be happy to give the source if that would help.
Thanks
