Buschfunk
14 years agoFrequent Contributor
Schema compliance fails with xs:anyAttribute
Observed in version: soapUI Pro 4.0.1
An XSD referenced by the imported WSDL defines the following complex type.
The SOAP response contains:
When activating the schema compliance assertion soapUI marks this part of the response as invalid with a hint that the attributes "Kennung" and "Praefix" are not allowed. As far as I can read the XSD (http://www.w3.org/2006/03/addressing/ws-addr.xsd) the instructions "any" and "anyAttribute" define possible extensions, i.e. the above response should be valid to the schema.
Or am I missing something?
Sincerely,
Robert
An XSD referenced by the imported WSDL defines the following complex type.
<xs:complexType name="ReferenceParametersType" mixed="false">
<xs:sequence>
<xs:any minOccurs="0" maxOccurs="unbounded" processContents="lax" namespace="##any"/>
</xs:sequence>
<xs:anyAttribute processContents="lax" namespace="##other"/>
</xs:complexType>
The SOAP response contains:
<ns3:To>
<Address>http://feature.not.implemented.yet</Address>
<ReferenceParameters Praefix="dbs" Kennung="99100100"/>
</ns3:To>
When activating the schema compliance assertion soapUI marks this part of the response as invalid with a hint that the attributes "Kennung" and "Praefix" are not allowed. As far as I can read the XSD (http://www.w3.org/2006/03/addressing/ws-addr.xsd) the instructions "any" and "anyAttribute" define possible extensions, i.e. the above response should be valid to the schema.
Or am I missing something?
Sincerely,
Robert