wkriski
09-04-2003, 11:57
I noticed when we receive SOAP responses, attributes such as xsi:type ="String" have been added to all the elements in the SOAP body such as:
<item xsi:type="sc1:SharedDataPoolType">
<fieldName xsi:type="xsd:string">majorActivityDescription</fieldName>
<value xsi:type="xsd:string">This business distributes bananas.</value>
</item>
However, using the WSDL and associated schemas used for the input/output parameters these attributes weren't there. So now instead of IS representing an XML element as a string it's representing it as a document with 2 attributes (*body and @xsi:type) so nothing's mapping correctly. Is this standard encoding practice in SOAP and if so is there a way to account for this in the flow. (ie we don't want to have to remap everything)
<item xsi:type="sc1:SharedDataPoolType">
<fieldName xsi:type="xsd:string">majorActivityDescription</fieldName>
<value xsi:type="xsd:string">This business distributes bananas.</value>
</item>
However, using the WSDL and associated schemas used for the input/output parameters these attributes weren't there. So now instead of IS representing an XML element as a string it's representing it as a document with 2 attributes (*body and @xsi:type) so nothing's mapping correctly. Is this standard encoding practice in SOAP and if so is there a way to account for this in the flow. (ie we don't want to have to remap everything)