If I (as a Xindice user) want to add a new XMLRPC method to the server, I think I need to define a class inside the org.apache.xindice.server.rpc.messages domain, correct? Personally, I'd like to see some way to create more domain specific methods. I don't really want to add my personal classes to the 'official' xindice namespace, since they really have more to do with my application than with xindice.
One possible solution would be for the RPCMessageInterface class to read a configuration file on startup which would map RPC method names to class names that service that method. This is vaguely reminiscent of the Apache server's ability to map URIs to different handlers or shared objects. I haven't thought about this a lot, but I like configuration files that allow users (or administrators) to alter the "out of the box" behavior. Does that make sense? If so, what do people think about it? dave -----Original Message----- From: Kurt Ward [mailto:[EMAIL PROTECTED] Sent: Thursday, December 05, 2002 4:51 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: xml-rpc messages > 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
