Hi Andrew
Thanks.
I am with you to step 10. I did build (1.1b3) from source so I have
config\commands.xml
Still the command line tool does not work. What I do not understand is: If
Xindice is running as a
plug-in under Tomcat, what should then CLASSPATH be set to? Running Xindice 1.0
CLASSPATH was set to
C:\Xindice\xml-xindice-1.0\java\lib\Xindice.jar
Xindice 1.1b3 does not have this .jar file
Kind Regards
Kim Daugaard
[EMAIL PROTECTED]
.com To: xindice-users@xml.apache.org,
[EMAIL PROTECTED]
cc:
01/27/2004 02:13 Subject: Re: Xindice 1.1b3
install/configuration frustrations on Windows XP
PM
Please respond
to xindice-users
In a message dated 1/27/2004 12:44:55 PM GMT Standard Time, [EMAIL PROTECTED]
writes:
11. Join me in waiting for an answer to how to get the Xindice 1.1 command
line tool working. :)
Kim,
I have solved it - at least for my set up. The necessary files are NOT in
EITHER of the zipped war
or zipped jar binary files!!! So, if I have grasped this correctly although
binaries for Windows are
made available for download they don't contain the necessary files to actually
run the command line
interface.
I downloaded the source zip file and had a look inside it using WinZip and
noticed it had the magic
config\commands.xml so I unzipped and installed it in X:\xindice-1.1b3,
indicating Yes To All to
overwrite files already there from the zipped war and jar downloads.
I ran a xindice command from the command line and it all works - at least it
will create a test
collection.
Just typing
xindice
at the command line gives a response indicating parameters etc that the command
line tool will
accept.
Then if I use the browser to access
http://localhost:8080/xindice/?/db/system/SysConfig&database.xml
I can see that a test collection has been added to the database.
Hm ... I wasted about 8 hours trying to get binaries to work which didn't have
the necessary files
in them to make the command line interface work.
Hm.
Andrew Watt