rtomasso
14 years agoNew Contributor
Adding <fault> to wsdl breaks parsing for WSI compliance.
Using SoapUI 4.0.1 on XP Pro.
Updating a wsdl file to include the mention of a soap fault our system may return, I add this block within <wsdl:binding>
Updating the definition works, I can run all the operations with proper results.
Running the WSI-compliance on the updated wsdl I get a new failure message that minOccurs is not valid for <element>
(the WSI-compliance was previously passing).
Updating a wsdl file to include the mention of a soap fault our system may return, I add this block within <wsdl:binding>
<wsdl:fault name="Fault">
<soap:fault name="Fault" use="literal" />
</wsdl:fault>
Updating the definition works, I can run all the operations with proper results.
Running the WSI-compliance on the updated wsdl I get a new failure message that minOccurs is not valid for <element>
(the WSI-compliance was previously passing).
Assertion: BP2122
Result failed
Failure Message
A wsdl:types element contained a data type definition that is not an XML schema definition.
Failure Detail Message
Error: s4s-att-not-allowed: Attribute 'maxOccurs' cannot appear in element 'element'.
Error: s4s-att-not-allowed: Attribute 'minOccurs' cannot appear in element 'element'.