If (1) has a context path of /xindice, and maps to URI xmldb:xindice//localhost:8080/db/, it would imply that the path of /xindice is taken for granted by Xindice. Then why not stick your second database _before_ the first in the Tomcat config file, at a context path of /xindice/second/, and then you may be able to get at your second database via xmldb:xindice//localhost:8080/second/db/.
Just a thought.
Upayavira
P.S. I think this thing about the /xindice bit being implicit might explain why I couldn't get the servlet version working myself!
[EMAIL PROTECTED] wrote:
Hi,
I\\\'m a newbie in Xindice and I have question, the solution is might simple for on of you.
Please imagine the following situation:
1. I have deployed a Xindice war file to a Tomcat 4.1.29 installation. <context path=\\\"/xindice\\\" docBase=\\\"xindice-1.1b2\\\" ...>
system.xml:
<root-collection dbroot=\\\"./db/\\\" name=\\\"db\\\" use-metadata=\\\"on\\\"> 2. I have deployed a second Xindice war file
<context path=\\\"/xindice2\\\" docBase=\\\"xindice-1.1b2_2\\\" ...>
system.xml:
<root-collection dbroot=\\\"./db/\\\" name=\\\"db2\\\" use-metadata=\\\"on\\\"> 3. I have started Tomcat and both databases work properly (tomcat output)
4. With the Xindice command line tool I\\\'am able to access the first database: e.g.: xindice lc -c xmldb:xindice://localhost:8080/db
5. It also works with the Java Example1.java file: collection = getCollection(\\\"xmldb:xindice://localhost:8080/db/register\\\");
Now my question. How can I access and how must the url look like in order to access the xindic2 database db2.
Thanx in advance for sour support
Thorsten