> "It would be nice to have the xmlrpc endpoint configurable also." > What do you mean? Currently, an xmlrpc user invokes the 'run' method with a > message parameter with the details of which class to use and the parameters > to pass. By xmlrpc endpoint, do you mean 'run'?
The url endpoint, such as http://localhost:8080/Xindice. I am not terribly familiar with servlets, but say I wanted both xmlrpc and soap API's available. The both run off of an HTTP POST operation, so an easy way provide each with it's own mapping would be nice. > As a second question, in Xindice 1.0, we had the 'db' name as the > handlerName (to use the terminology from > http://xml.apache.org/xmlrpc/server.html). Why did we abandon that in favor > of this RPCMessageInterface being registered as the '$default'? I'm not > particularly opposed to this change, but I can't seem to find where this was > discussed, and I don't intuitively understand why we redesigned the XMLRPC > interfaces in this way. Good question, but I don't know the answer. Kurt
