> What bothers me a little is that in a class placed in the client package, you > will have to import org.apache.xindice.SERVER.rpc.* classes. Should a client > _import_ server classes, that's my question? I don't particularly like this > idea, but it's maybe me. > > That's the reason why I thought of moving the server.rpc classes into > client.xmlrpc. And since I don't have many classes left in the server > package, I thought of removing the server package and define the "accessor" > (name to be changed) hierarchy. > > -Vladimir > > ===== > Vladimir R. Bossicard > Apache Xindice - http://xml.apache.org/xindice
There is no xmlrpc *client* in CVS. Maybe that is the confusion here. The server.rpc package defines the xmlrpc server that is used with Tomcat (or other app server). For a user to use an xmlrpc client, all he needs to do use the Apache xmlrpc jar. You do not need any packages from Xindice. There is an XML:DB driver (client, if you want to call it that) that uses an internal xmlrpc client. To use the driver, all you would need is the Apache xmlrpc jar, and the XML:DB jars. Kurt
