more "things you find out later" -----Original Message----- From: Kimbro Staken [mailto:[EMAIL PROTECTED] Sent: Saturday, June 15, 2002 1:48 AM To: [EMAIL PROTECTED] Subject: Re: building just client xindice
The system already uses a different ORB for the client and the server. The client uses the built in ORB that comes with the JVM and the server uses OpenORB. I'd really avoid changing the ORB on the client if you can avoid it. Also be aware, CORBA is deprecated and will be cut out of the system before too much longer. Of course due to the architecture it could always be added back in as a component, but somebody else will have to pick up development of it. For a standalone client I think you need org.apache.xindice.client, org.apache.xindice.xml, org.apache.xindice.util and for the command line tools org.apache.xindice.tools. I've never tried building a standalone client. If you get it working though, hopefully you can contribute it back as this is something we really should have had a long time ago. On Friday, June 14, 2002, at 10:55 AM, Vandewart, Ruthe Lynn wrote: > I am just starting to add Xindice to our application which relies on > ORBacus > for its CORBA implementation. The Xindice README states "The CORBA ORB > used > by the server is now easily pluggable. So far, JacORB and OpenORB are > known > to work" so I am going to try ORBacus only for the client application. > Since the naming systems of the jidl generated files differs among CORBA > implementations, this is not as simple as it seems at first. I really > really need a separate build capability for the client classes that doesnt > mess with the server build. Can anyone indicate to me which classes are > not > involved in the client end of things? > > > > Kimbro Staken Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ Apache Xindice native XML database http://xml.apache.org/xindice XML:DB Initiative http://www.xmldb.org
