Cheong Chung Onn wrote:
Thanks Upayavira,
I am new to wiki, i guess i need to learn about it first before posting anything to the xindice :)
Try it. Believe me, using a Wiki isn't hard. But yes, we've got to have something to say on a Wiki before we start using one!
Upayavira
chung-onn
On 22 Feb 04, at 1:33 AM, Upayavira wrote:
Cheong Chung Onn wrote:
Hi Philipp and Vadim,
I thank you both for helping me get going with xindice. I really find the docs for xindice very scare and scattered all over the places and very difficult for a newbie like me to get going especially the setting up of the examples.
I would like to contribute to the docs once i get to know xindice better, but i don't know how. Please let me know how i can do this.
Start by working on the Wiki, at http://wiki.apache.org/xindice. If you produce some good stuff, it can be moved into the main Xindice docs - do enough, and you could become able to commit docs to the main docs yourself. Documentation writers are always appreciated, and in short supply.
With best wishes,
Upayavira
Thanks again. chung-onn
On 21 Feb 04, at 3:20 AM, Vadim Gritsenko wrote:
Philipp Dev wrote:
Hi
I must admit, that I'm also a bit confused with this behaviour.
Your xindice command line tool is looking for a xindice webapp at port 8888
[DEBUG] CollectionImpl - -Using URL: 'http://127.0.0.1:8888/xindice/'
If you start your built in jetty like described here http://wiki.apache.org/xindice/InstallationBuiltInJetty
and do the same command you will get the wanted result which normaly would
look like
C:\java>xindice lc -c /db trying to register database
system meta yourcollectionhere
Total collections: 3
But a question bother me:
Wasn't the command line tool independant from the server in earlier builds?
Command line tool by default connects to the remote xindice server via xmlrpc. It has an option of accessing local database files using option -l:
xindice lc -l -c /db
AFAIR, it always was this way.
Vadim
