I thought it was yet another problem with the web service not declaring a SOAP fault on an operation, but now I am not sure. The SOAP operation listed a Fault that was of a base type of the fault that was thrown. When ClientFaultConverter iterated over the operation's listed faults it did not match. So it threw a generic SoapFault. So what does SOAP 1.1 standard say? Should a WSDL list each fault even if they are extensions of some base element? Or should listing a base element as the fault be acceptable, inheriting not just form, but function? If the latter, then ClientFaultConverter would need to be amended in some fashion. Thank you for any insight on this.

Fred

Reply via email to