xml-xindice-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Kavanaugh" <kkavana...@teletrol.com>
Subject RE: Moving from Xindice 1.0 -> 1.1
Date Fri, 05 Sep 2003 18:48:05 GMT

I am a little closer.

a) Installed ant
b) Installed cvs
c) did a build

mind you all this to get a working command line tool for importing large file sets.

A couple of question(s), for clarification sake, before proceeding.

Embed: I assume this means I am in the same address space talking to the same VM so don't
go through the overhead
of establishing a HTTP socket connection? Correct? 

If correct does the -l switch, when running the xindice.bat file, which invokes the main()
in class org.apache.xindice.tools.XMLTools, I know I could continue perusing the sources and
figure this out, but alas work needs to get done, mean embedded or does it mean hey I'm local
use the loopback ip vs going out over the net?

What does the -d switch point to? Real example please.

And finally to the question. I am trying to import the file sets we were using in 1.0. Note
these are now out on a flat file system. So I thought I could use the same command line invoke,
but I get this...

C:\home\kurt\xml-xindice\bin>xindice.bat import -c /db -f c:\staging\Company_A -e xml
[DEBUG] DatabaseImpl - -Using SAX Driver: 'xerces'
[DEBUG] DatabaseImpl - -Using Service Location: '/xindice/'
[DEBUG] CollectionImpl - -Using URL: ''
XMLDB Exception with code 0

Which before would create a collection with a name of Company_A. In addition what is the port
8888 gig? How do I specify a non standard port? Is there a connection string kind of thingie
like in ODBC/JDBC land?

ie Host:Port:DbInstance:UserName:Password

-----Original Message-----
From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
Sent: Thursday, September 04, 2003 2:51 PM
To: xindice-users@xml.apache.org
Subject: Re: Moving from Xindice 1.0 -> 1.1

Kurt Kavanaugh wrote:

>Kurt Kavanaugh wrote:
>>I am moving from 1.0 to 1.1. I am not concerned with backward compatibility.... that
much. I am however concerned with getting up and running and understanding the new packaging
and configuration elements.
>>I have the server up and running, in theory, by installing the war file...
>>Under tomcat 4.1.27
>>My db is present and accounted for. I am using jdk 1.4.1.
>>My question is this... where has the bin gone? to administer and test from the command
line. What are the other pieces?
>war distribution does not has xindice command line tool. 
>Understood. So all admin is done through exercising a set of java api's? And these java
api's are javadoc'd where?

If you want to use APIs... I'm not exactly sure what distribution 
includes javadoc. You can get src distribution and build javadoc.

>Currently, you can download CVS and run xindice tools from there connecting to your 
>xindice instance runnign in tomcat.
>You mean currently you can download cvs, use ant to build the bin tools. the resulting
tools then know how to converse
>with tomcat on port 8080 vs 4080 and use XML-RPC vs CORBA.


>>Any help in understanding the packaging and configuration aspects of the 1.1 environment
vs the 1.0 would be helpful.
>1.1 is beta, so packaging is not final, improvements still can be done.
>Understood. Perhaps I could be of help here...

If you have an idea how to package xindice tool into war distribution, 
send a patch to -dev list.


View raw message