If a request contains <FieldA>outside cdata <![CDATA[inside <data> cdata]]></FieldA>, the transformed string will become <FieldA>outside cdata </FieldA>. I.e. the CDATA segment is completely missing in the result.

On WLS 10.3.4 deployed a webservice and invoking it from client on the same machine.Segment in soap request ignored when transformed to a string.

If a request contains <FieldA>outside cdata <![CDATA[inside <data>
cdata]]></FieldA>, the transformed string will become <FieldA>outside cdata
</FieldA>. I.e. the CDATA segment is completely missing in the result.

Below is the snippet from WLS 10.3.4 log with webservice debug enabled

<ServletDebugUtil.printRequest:34>

• • S T A R T I N P U T S T R E A M **
    Sep 13, 2011 4:01:13 PM com.sun.xml.ws.transport.http.HttpAdapter
    fixQuotesAroundSoapAction
    INFO: Received WS-I BP non-conformant Unquoted SoapAction HTTP header:
    INFO com.sun.xml.ws.transport.http.HttpAdapter Received WS-I BP
    non-conformant Unquoted SoapAction HTTP header:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body>
<echoRequest xmlns="http://test.ibm.com/xsd">
<arg0>outside cdata <![CDATA[<data>inside cdata</data>]]></arg0>
</echoRequest>
</soapenv:Body>
</soapenv:Envelope>** E N D I N P U T S T R E A M **

When trying to parse this xml with javax.xml.transform.Transformer notice
below snippet on WLS 10.3.4

=====================Request payload================

<?xml version="1.0" encoding="UTF-8"?><echoRequest
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns="http://test.ibm.com/xsd">
<arg0>outside cdata </arg0>
</echoRequest>

====================================================
However this seems to work fine in prior releases of weblogic from WLS 10.3 till 10.3.2

It appears to be a bug in woodstox parser.It was fine in woodstox3.2.5.The issue seems to stem after from 4.0.5