> 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.
Good point. This could also be a replacement for XMLObjects instead of digging it out of the 1.0 trunk and still allow users to extend the server with stored procedure type messages. > 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? It would be nice to have the xmlrpc endpoint configurable also. Kurt
