you're right.  changing the rpc code to fetch from port 8888 worked.  i've
sent a message to xindice-dev asking if we should change the code to call
port 8888 or change the jetty configuration to start on port 8080.

thanks
dave


-----Original Message-----
From: Jose Ramon Revuelta [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2003 2:03 PM
To: xindice-users@xml.apache.org
Subject: RE: cmdline tool functional w/ 1.1b2?


I'm haven't used Xindice with Jetty (which is used if you start Xindice with
the "start" script) if this is the case, it is listening to port 8888
instead of 8080 which is the default for Tomcat. So I think you need to
change either the client to look at port 8888 or the startup on Jetty to
listen to port 8080.

Saludos,
José Ramón




-----Original Message-----
From: Viner, David [mailto:[EMAIL PROTECTED]
Sent: Lunes, 04 de Agosto de 2003 04:00 p.m.
To: 'xindice-users@xml.apache.org'
Subject: RE: cmdline tool functional w/ 1.1b2?


After some more poking through the source code, I noticed that the xindice
commandline tool is attempting to contact Xindice via XML RPC on port 8080.
However, it appears to me that nothing is listening on port 8080 on my
machine.  Is there something else that I need to start which listens on port
8080?

dave

-----Original Message-----
From: Viner, David [mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2003 12:20 PM
To: Xindice-Users (E-mail)
Subject: cmdline tool functional w/ 1.1b2?


Hi,
        I have rebuilt my Xindice from the current CVS sources.  I start it
fine using:

%XINDICE_HOME%\xindice.bat start

Everything looks ok, and I can browse http://127.0.0.1:8888/xindice?/db
without a problem.  

However, if I try to use the commandline tool, I get this error:

D:\xindice\apache-cvs\xml-xindice>bin\xindice lc -c /db
[DEBUG] xmlrpc - -serviceLocation=</xindice/>
ERROR : Collection not found!
D:\xindice\apache-cvs\xml-xindice>


>>From looking in the archives, the problem has been described before.  But
the only answer was to use Xindice thru Cocoon.  Has anyone gotten the
commandline tool to work with 1.1b2?

thanks
dave

Reply via email to