Forum Discussion

pascalSoap's avatar
pascalSoap
Occasional Contributor
14 years ago

Assertion Schema Compliance failed -"not valid NCName error"

Hello , I have an error on a Schema Compliance assertion which failed with the message : " ... line 4: Invalid QName value: Localname not a valid NCName in 'GetListOfDocbaseFault:3' ... " ...
mlenosgrande's avatar
mlenosgrande
Contributor
14 years ago
see the wsdl file. If it is a customized soapfault this might be declare along with wsdl:input, wsdl:output and wsdl:fault
Example : 
    
<wsdl:operation name="CloneStuff">
      <wsdl:input message="tns:CloneStuffRequest" name="CloneStuffRequest" />
      <wsdl:output message="tns:CloneStuffResponse" name="CloneStuffResponse"/>
      <wsdl:fault message="tns:KebabWsFault"  name="KebabWsFault"/> 
  </wsdl:operation>


The client may have no problem because they are not using fault at all to catch some special fields or are already aware how the structure of the fault .

So they can dig into if needed to retrieve customized elements in the soapfault (errorCode ...). (faultcode is a standard one for example )