How to pass a xml CDATA in string element when OSB calling a webservice?

Question

How to pass a xml CDATA in string element when OSB calling a webservice?
I have a business service (biz) that route to operation of a webservice.
A example of request to this webservice legacy:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eg="example">
<soapenv:Header/>
<soapenv:Body>
<ex:execute>
<ex:arg><![CDATA[<searchCustomerByDocumentNumber>
<documentNumber>12345678909</documentNumber>
</searchCustomerByDocumentNumber>]]></ex:arg>
</ex:execute>
</soapenv:Body>
</soapenv:Envelope>
the type of ex:arg is a string.
How to pass this CDATA structure to webservice in OSB?

Answer 1

Steps to solve this problem:
1. Create a XML Schema. E.g.:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
     elementFormDefault="unqualified">
     <xs:complexType name="searchCustomerByDocumentNumber">
          <xs:sequence>
               <xs:element name="documentNumber" minOccurs="0">
                    <xs:annotation>
                         <xs:documentation>
                         </xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                         <xs:restriction base="xs:string" />
                    </xs:simpleType>
               </xs:element>
     </xs:sequence>
     </xs:complexType>
     <xs:element name="searchCustomerByDocumentNumber" type="searchCustomerByDocumentNumber"></xs:element>
</xs:schema>
With this XSD, the XML can be generate:
<?xml version="1.0" encoding="UTF-8"?>
<searchCustomerByDocumentNumber xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="searchCustomerByDocumentNumber.xsd">
<documentNumber>documentNumber</documentNumber>
</searchCustomerByDocumentNumber>
2. Create a XQuery to create a searchCustomerByDocumentNumber ComplexType. E.g.:
(:: pragma bea:global-element-return element="searchCustomerByDocumentNumber" location="searchCustomerByDocumentNumber.xsd" ::)
declare namespace xf = "http://tempuri.org/NovoSia/CreateSearchCustomerByDocumentNumber/";
declare function xf:CreateSearchCustomerByDocumentNumber($documentNumber as xs:string)
as element(searchCustomerByDocumentNumber) {
<searchCustomerByDocumentNumber>
<documentNumber>{ $documentNumber }</documentNumber>
</searchCustomerByDocumentNumber>
declare variable $documentNumber as xs:string external;
xf:CreateSearchCustomerByDocumentNumber($documentNumber)
3. In your stage in pipeline proxy add a assign calling the XQuery created passing the document number of your payload.
Assign to a variable (e.g.: called searchCustomerByDocumentNumberRequest)
4. Create another XQuery Transformation (XQ) to create a request to the webservice legacy. E.g.:
<ex:arg>{fn-bea:serialize($searchCustomerByDocumentNumberRequest)}</ex:arg>
For more information about xquery serialize function:
41.2.6 fn-bea:serialize()
You can use the fn-bea:serialize() function if you need to represent an XML document as a string instead of as an XML element. For example, you may want to exchange an XML document through an EJB interface and the EJB method takes String as argument. The function has the following signature:
fn-bea:serialize($input as item()) as xs:string
Source: http://docs.oracle.com/cd/E14571_01/doc.1111/e15867/xquery.htm