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]
