Quantcast
Channel: SCN: Message List - SAP Manufacturing Integration and Intelligence (SAP MII)
Viewing all articles
Browse latest Browse all 4841

XML validation in SAP MII Workbench alters XML structure

$
0
0

Working with MII 14 SP5 Patch 3 we found that if we check the “Validate XML on execution” ONLY for outputs the xml created is the same as MII 12. The inputs does not matter if you check the validation or not. But, what we found is that if this validation give us an error if we run the web service with SoapUI or directly with the external application that was using the web service using MII 12, this is the error:

 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soap:Body>

      <soap:Fault>

<faultcode>soap:Client</faultcode>

         <faultstring>Transaction threw an unrecoverable exception:</faultstring>

      </soap:Fault>

   </soap:Body>

</soap:Envelope>

 

If the validation is removed the transaction runs fine but the xml is different.

This is a portion of the xml with the validation checked:

<s:complexType name="Row">

     <s:sequence id="RowSequence">

          <s:element name="OT_GET_ORDERS" minOccurs="1" maxOccurs="1">

              <s:complexType>

                    <s:sequence>

                             <s:element ref="mii0:O_GET_ORDERS"/>

                    </s:sequence>

               </s:complexType>

          </s:element>

          <s:element name="OT_GET_ORDERS_MESSAGES" minOccurs="1" maxOccurs="1">

               <s:complexType>

                    <s:sequence>

                         <s:element ref="mii0:O_GET_ORDERS_MESSAGES"/>

                    </s:sequence>

               </s:complexType>

          </s:element>

     </s:sequence>

</s:complexType>


This is the portion of the xml with no validation checked:

<s:complexType name="Row">

     <s:sequence id="RowSequence">

          <s:element name="OT_GET_ORDERS" type="s:string" minOccurs="1" maxOccurs="1"/>

          <s:element name="OT_GET_ORDERS_MESSAGES" type="s:string" minOccurs="1" maxOccurs="1"/>

</s:sequence> </s:complexType>


I haven't found documentation about, and I need to understand why this validation only affect the output and not the inputs that uses XSD.

I appreciate your help.

 

Nancy Rocha


Viewing all articles
Browse latest Browse all 4841

Trending Articles



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