Agreed -- it would be nice if Axis provided a little more reason in the <soapenv:Text> element. Please file a JIRA requesting this enhancement.
As for solving you immediate problem, I suggest you capture the generated input SOAP message and discover for yourself where the problem lies. Anne On 8/25/06, Daniel Bridenbecker <[EMAIL PROTECTED]> wrote:
I have a custom Deserializer (i.e. extends DeserializerImpl) and it throws a nice message about what is wrong, but the fault returned from the server is: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body> <soapenv:Fault> <soapenv:Code> <soapenv:Value>soapenv:Sender</soapenv:Value> <soapenv:Subcode xmlns:ns1="http://www.w3.org/2003/05/soap-rpc";> <soapenv:Value>ns1:BadArguments</soapenv:Value> </soapenv:Subcode> </soapenv:Code> <soapenv:Reason> <soapenv:Text xml:lang="en">string</soapenv:Text> </soapenv:Reason> <soapenv:Detail> <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/";> BRIDEN-DELL2 </ns2:hostname> </soapenv:Detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> Where this does tell me that one of the arguments to the method call is bad, it doesn't tell me something like "Invalid date format". It doesn't even tell which argument is bad. Does anyone know how I could get Axis to use the message in the exception? Thanks. Daniel Bridenbecker Solution Engineering, Inc. 425-402-3690 [EMAIL PROTECTED] --------------------------------------------------------------------- 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]
