Support Article

Connect SOAP MTOM enabled fails Pega 7.2.2 version of HFix-28742

SA-35749

Summary



After upgrading to Pega 7.2.2 from Pega 7.2.1 Connect SOAP request messages are failing on back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element"

Examining the SOAP message sent from Pega server, it might be that the base64binary is not being substituted correctly with the expected "XOP Include" element.


Error Messages



rio-training: MPGW_Webservice_Security_Routing : Error occured for message with instance-id: ABC-WORK APP-2528-DS_7f6f522d-bbbd-4fa0-b46e-b969783ee01e error details: Attemped resouces accessed: /domain-http-servlet/IPRDSDocumentService/IPRDSDocumentDocumentPortImpl Error details: http://a.a.a.a:10060/domain-http-servlet/DocumentService/IPRDSDocumentDocumentPortImpl: xop 3.2.2.a: xop:Include must be the sole child of element {http://abc/CIM/Common/2}Document of type {http://abc/2001/XMLSchema}base64Binary.

Steps to Reproduce



Not Applicable


Root Cause



While validating an MTOM/XOP optimized message, an xop:Include element was encountered in a simple type context, inside an element with other children element.

The xop:Include element may only be used to replace base64 encoded content that is the sole child of its parent element, and must completely replace that content.

Therefore, no text, comments, processing instructions, or other elements are allowed surrounding the xop:Include element.

Resolution



Apply HFix-33171.

Published April 10, 2017 - Updated October 8, 2020

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.