On 1/4/07, Andrew Norman <[EMAIL PROTECTED]> wrote:
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?
This is *very* intended. I never understood the rationale. Exceptions are the standard way to handle errors in Java, so why should one prefer a different manner? Jochen -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
