Expand my Community achievements bar.

CDATA and envelope format sensitivity

Avatar

Former Community Member

Hello,

I am using standard LiveCycle component/service "WebService" in LiveCycle process to call a Web service.
In SOAP response is CDATA section with xml document that I need to work with.

In Web-service component properties is section "CDATA list" which should parse all CDATA sections of soap-response to a list variable.
It works well if the service returns (A)-type response format (see below), but doesn't parse anything for (B)-type.

So - can WebService component parse CDATA section from generic soap/xml format or does it require (A)-like format ?
Thanks

A) works well
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Body>
      <invokeResponse xmlns="http://adobe.com/idp/services">
         <doc xsi:type="ns1:XML" xmlns:ns1="http://adobe.com/idp/services">
            <document>
                <![CDATA[<?xml version="1.0"?>
                    <foo><alfa>aaa</alfa><beta>bbb</beta></foo>
                ]]>
            </document>
         </doc>
         <foo>Hello world</foo>
         <i>0</i>
      </invokeResponse>
   </soapenv:Body>
</soapenv:Envelope>

B) does not work
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <SOAP-ENV:Body>
      <ns1:someMethod SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="yyy">
         <return xsi:type="xsd:string">
        
         <![CDATA[
        
            <?xml version="1.0" encoding="UTF-8"?>
            <response id="0" xsi:noNamespaceSchemaLocation="loc.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            ...   
            </response>
        ]]>
       
        </return>
      </ns1:someMethod>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

0 Replies