Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

Additional Attributes Needed For an External Definition

$
0
0

A business partner (receiving system) gave us their definition of their XML structure. We imported it used it in our mapping but the integration still fails. This is because in one particular field they need additional attributes.

 

The structure that they gave us:

 

From the XSD

<xs:complexTypename="CustomFieldAnswer">

https://apac-test.proconchevron.com/ProConServiceHost/CommunicationService.svc?xsd=xsd0     <xs:sequence>

https://apac-test.proconchevron.com/ProConServiceHost/CommunicationService.svc?xsd=xsd0          <xs:elementname="Value" type="xs:anyType" nillable="true" minOccurs="0"/>

     </xs:sequence>

</xs:complexType>

 

So this would look like as:

 

<ns2:CustomField>

<ns2:Name>CWT20502400</ns2:Name>

<ns2:Answer>

<ns2:Value >1</ns2:Value>

</ns2:Answer>

</ns2:CustomField>

 

 

But what they need is:

<ns2:CustomField>

<ns2:Name>CWT20502400</ns2:Name>

<ns2:Answer>

<ns2:Value i:type="a:string" xmlns:a="http://www.w3.org/2001/XMLSchema">1</ns2:Value>

</ns2:Answer>

</ns2:CustomField>

 

So generally, there's an additional

 

i:type="a:string" xmlns:a="http://www.w3.org/2001/XMLSchema"

 

Is this something that PI should insert or add or should be added from their XSD, which we would then import after?

 

Thanks


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>