14 years ago
Schema Compliance assertion fails for custom data types
Hi,
In soapUI, we are checking the response generated by the SDK API are schema compliant are not for this we are using schema compliance assertion. But for the below xml format, schema compliance assertion is failing.
All the APIs which have the return type as “Map” is getting failed due to schema compliance assertion.
For instance,
Below mentioned is the response xml of start refresh API which returns object of type Map.
Schema assertion is getting failed in the below highlighted lines.
<table>
<key s1:type="s2:long" xmlns:s1="http://www.w3.org/2001/XMLSchema-instance" xmlns:s2="http://www.w3.org/2001/XMLSchema">76150</key>
<value xsi:type="ns8:RefreshStatus" xmlns:ns8="http://refresh.core.soap.yodlee.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">REFRESH_ALREADY_IN_PROGRESS</value>
</table>
<table>
<key s3:type="s4:long" xmlns:s3="http://www.w3.org/2001/XMLSchema-instance" xmlns:s4="http://www.w3.org/2001/XMLSchema">76151</key>
<value xsi:type="ns8:RefreshStatus" xmlns:ns8="http://refresh.core.soap.yodlee.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">REFRESH_ALREADY_IN_PROGRESS</value>
</table>
We are facing this issue in soapUI Pro version 4.0.1.Please let us know how can we handle such errors.
Regards,
Pavithra
In soapUI, we are checking the response generated by the SDK API are schema compliant are not for this we are using schema compliance assertion. But for the below xml format, schema compliance assertion is failing.
All the APIs which have the return type as “Map” is getting failed due to schema compliance assertion.
For instance,
Below mentioned is the response xml of start refresh API which returns object of type Map.
Schema assertion is getting failed in the below highlighted lines.
<table>
<key s1:type="s2:long" xmlns:s1="http://www.w3.org/2001/XMLSchema-instance" xmlns:s2="http://www.w3.org/2001/XMLSchema">76150</key>
<value xsi:type="ns8:RefreshStatus" xmlns:ns8="http://refresh.core.soap.yodlee.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">REFRESH_ALREADY_IN_PROGRESS</value>
</table>
<table>
<key s3:type="s4:long" xmlns:s3="http://www.w3.org/2001/XMLSchema-instance" xmlns:s4="http://www.w3.org/2001/XMLSchema">76151</key>
<value xsi:type="ns8:RefreshStatus" xmlns:ns8="http://refresh.core.soap.yodlee.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">REFRESH_ALREADY_IN_PROGRESS</value>
</table>
We are facing this issue in soapUI Pro version 4.0.1.Please let us know how can we handle such errors.
Regards,
Pavithra