[CAMEL-9246] camel-cxf proxy with MTOM does not get attachment back when RPC/literal style WSDL used

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.15.1
• Fix Version/s: 2.15.5, 2.16.2, 2.17.0
• Component/s: camel-cxf

Environment

CXF 3.0.4

• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: Joe Luo
• Created: 22/Oct/15 18:45
• Updated: 16/Nov/15 07:45
• Resolved: 16/Nov/15 07:45

Description

I have a camel-cxf proxy test case with MTOM enabled. The WSDL used in the project is RPC/Literal style. However, I was unable to get attachment back via response. Please take a look at the test case for more detail.

After some debugging, it looks like that camel-cxf producer did get attachment back. However, there were two attachment related parts. One part had no attachment (empty) but had correct "Content-ID". The other part did contain entire attachment but had a rather different "Content-ID". For instance:

19:30:47,110 | INFO  | qtp565617691-367 | IMtomExample                     | 118 - org.apache.cxf.cxf-core - 3.0.4.redhat-620133 | Outbound Message
---------------------------
ID: 63
Response-Code: 200
Encoding: UTF-8
Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:f108bc3f-549a-4baa-ab00-757ff837aacf"; start="<[e-mail]>"; start-info="text/xml"
Headers: {accept-encoding=[gzip,deflate], breadcrumbId=[ID-jluomac-52985-1445511717614-11-8], Host=[localhost:7777], Server=[Jetty(8.1.15.v20140411)], User-Agent=[Apache-HttpClient/4.1.1 (java 1.5)]}
Payload: --uuid:f108bc3f-549a-4baa-ab00-757ff837aacf
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: binary
Content-ID: <[e-mail]>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1:doMtomResponse xmlns:ns1="http://cxf.example.com/"><parameters xmlns:ns2="http://cxf.example.com/"><output>soapui-splash.png</output><dataLength>27186</dataLength><data><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:[e-mail]"/></data></parameters></ns1:doMtomResponse></soap:Body></soap:Envelope>
--uuid:f108bc3f-549a-4baa-ab00-757ff837aacf
Content-Type: image/png
Content-Transfer-Encoding: binary
Content-ID: <[e-mail]>
Content-Disposition: attachment;name="soapui-splash.png"

<-- soapui-splash.png binary attachment starts here -->
...
...
<-- soapui-splash.png binary attachment ends here -->

--uuid:f108bc3f-549a-4baa-ab00-757ff837aacf
Content-Type: image/png
Content-Transfer-Encoding: binary
Content-ID: <[e-mail]>
Content-Disposition: attachment;name="soapui-splash.png"

<-- no binary attachment here. empty -->

--uuid:f108bc3f-549a-4baa-ab00-757ff837aacf--
--------------------------------------

And the response message returned was:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <ns1:doMtomResponse xmlns:ns1="http://cxf.example.com/">
         <parameters xmlns:ns2="http://cxf.example.com/">
            <output>soapui-splash.png</output>
            <dataLength>27186</dataLength>
            <data>
               <xop:Include href="cid:[e-mail]" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
            </data>
         </parameters>
      </ns1:doMtomResponse>
   </soap:Body>
</soap:Envelope>

Because the response pointed to the "Content-ID" of

<xop:Include href="cid:[e-mail]" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>

and the parts identified by the "Content-ID: <[e-mail]>" was actually empty. Therefore, client can not get the attachment back.