"Aaron Smuts" <[EMAIL PROTECTED]> writes: > When you have a default handler why do you have to specify a method? I > made a xml-rpc lateral cache for JCS and created a default handler for > puts. I'm still working on it, but I ran into a problem with using a > default handler. I didn't specify a method on the send and it wouldn't > work. I specified a .junk method and the problem was solved.
The specification <http://xml-rpc.com/spec> requires a "methodName" element be sent in the body of the RPC data, where the "methodName" body is an textual identifier (rather than an actual Java method name). I can't off-hand think of a good way to pick the right method from a generic object which is being used as a XML-RPC handler. However, for those classes implementing org.apache.xmlrpc's XmlRpcHandler interface, I can't see any reason why the server couldn't fill this portion of the data if another handler cannot be found. If things aren't like this already, patches welcome. > Also, is there a problem returning null? I keep getting some eof error > when the remote methods return null. It may be something else. As per the specification <http://xml-rpc.com/spec>, null is not a valid return type. Patches improving any error handling of this behavior much appreciated. Daniel
