Upayavira wrote:
David Kensche wrote:
Upayavira wrote:
I have found that any changes to the database you make using the CLI will be lost if you are running another process that has connected to the database (servlet or embedded mode code). Stopping Tomcat, adding the collection/documents, and then restarting Tomcat, should work around this.
Now, I don't know whether this should be considered a bug. Probably should. It would certainly be useful to me if I could add stuff from outside my servlet environment.
Regards, Upayavira
That's definitely the case. I have a webapplication running, which reads an ontology from the db. Also I have a gui
running for access to the documents which are inserted by another application. The problem is that at least two
of those have to be running at the same time.
Have you tried it without the webapp running? Just to test whether we are talking about the same problem?
Regards, Upayavira
You were right.
As I said there are two contexts running on tomcat - xindice-1.1b3-dev and xindice. The tools and my applications
always access the xindice context. When I stop xindice-1.1b3-dev before making any changes to the database, the
changes persist. Why are there two contexts at all? And why one, which is not accessed by the tools? And how can
the xindice-1.1b3-dev context be running if it is is not accessed by any application?
Regards,
David