Geoff Howard wrote:
For now, though for purposes of reviving the samples quickly it may
be as easy as re-commiting a new db.script into the database block
with the changes in it.
IIUC hsql uses this file as its persistent store of data - when you
shut down, it gets overwritten with what is in memory. So, if you
make changes to the file,
then restart cocoon to reload the changes, they disappear. It was
awkward for me trying to contribute (read: I lost changes a few times
and am still getting over it emotionally ;) ) but that's not
happening much.
...and I assume it's get loaded when it comes up. So all we
need to do is to put a file into the webapp (at the right place)
so it gets loaded as it where shut down before, right?
That was my experience.
cool - so I'll fix it that way
--
Torsten
