Vadim Gritsenko wrote:
Georg Sauer-Limbach wrote:
There is the problem that changes to the database that are made
via the local interface (command line) are not reflected in a
running server instance, i.e. in Tomcat. Maybe this makes a
candidate for nice-to-fix?
No, this one does not. But bring in other suggestions :)
Regarding your problem. You should never attempt to open database
files from two processes, such as Tomcat & command line tool with -l
switch, since that will corrupt your database. If you are running
instance of db in Tomcat, use db URL in the command line to access
this running instance, instead of -l switch [1]:
./bin/xindice lc -c xmldb:xindice://localhost:8080/db
Thanks for the hint, I really should avoid the local calls.
I really used them only for the less typing :-)
BTW, have you tried the latest trunk? If you are using windows it
should prevent you from concurrently accessing same database files
from different processes. It does not work for me in OS X though...
When Xindice drops minimum java 1.3 requirement, we could use java
1.4's new file I/O to make file locking work on all platforms.
We are still using version 1.4b, and on Unix. It would certainly be
good to have the locking functionality on all systems. But I
understand it is difficult with Java 1.3.
Regards
Georg
