[ http://issues.apache.org/jira/browse/XMLRPC-66?page=comments#action_12378897 ]
Jochen Wiedmann commented on XMLRPC-66: --------------------------------------- I admit that you've got a point. On the other hand, the XML-RPC spec does neither allow to send custom elements (which might include the exception and be evaluated by the XmlRpcClient) nor does it attempt to specify the error messages contents. My personal opinion is: When in doubt, transfer more information. I'd leave this as it is. > Throwing exception to create RPC fault results in exception name transmitted > over the wire > ------------------------------------------------------------------------------------------ > > Key: XMLRPC-66 > URL: http://issues.apache.org/jira/browse/XMLRPC-66 > Project: XML-RPC > Type: Bug > Versions: 2.0 > Reporter: Oliver Cole > > If you throw an exception at any point in or below the named method in the > handler object registered with the XmlRpcServer object, like so, > throw new IllegalArgumentException("foobar"); > then the name of the exception is returned in the RPC fault sent over the > wire, like so: > <value> > java.lang.Exception: java.lang.IllegalArgumentException: foobar > </value> > This is of course, bad, as this is not implementation independant. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
