To provide more context to my last post: It looks like instead of returning the XmlRpcException as the result object, the XmlRpcException is thrown instead. Also worth noting is that the context of the error message has changed. Previously it was " java.lang.Exception: <packagename.actualInstantiatedExceptionClass>:" + the actual error message.
Now the message is just: "Failed to invoke method <method name> in class <your server side handler class>:" + the actual error message A couple of thoughts on the above behavior: * Is the original error message response used in XML RPC 2 rather than XML RPC 3 the desired XML-RPC error messaging format (I see this error messaging format documented in XML RPC based sites such as Blogger API http://www.blogger.com/developers/api/1_docs/xmlrpc_getUsersBlogs.html)? * Also I really don't like the use of the "Failed to invoke method <method name> in class <your server side handler class>:" message which is the message of the "false" error thrown by the XML-RPC reflection logic used for invoking Server side handler methods. It's a "false" message because in this case the target method was invoked and the actual exception thrown was originally a data-validation related exception in my application logic. Previously in 2.0 the method invocation based message was never park of the error message. Any thoughts? -Andrew -----Original Message----- From: Andrew Norman [mailto:[EMAIL PROTECTED] Sent: Thursday, January 04, 2007 12:13 PM To: xmlrpc-dev@ws.apache.org Subject: Noticed that the XML Rpc client in release 3 handles exceptions differently than in release 2 I've just upgraded from release 2 to release 3 and noticed a change in the behavior of how the XML RPC client is handling server side exceptions. Previously in release 2 the return object (in the case of exceptions) would actually be an XmlRpcException; however, with release 3 the object the client's return object is null. As a sanity check, I can see that the XMLServerSide code is actually creating the fault response. Is this behavior change between release 2 and 3 a bug or is it an intended change? -Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
