Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 30 May 2017 10:37:04 +0000 (UTC)
From: "Joerg Kessler (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13075736.1496119737000.319752.1496140624370@Atlassian.JIRA>
In-Reply-To: <JIRA.13075736.1496119737000@Atlassian.JIRA>
References: <JIRA.13075736.1496119737000@Atlassian.JIRA> <JIRA.13075736.1496119737444@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CXF-7388) Problem with MTOM in Camel-CXF
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 30 May 2017 10:37:09 -0000


     [ https://issues.apache.org/jira/browse/CXF-7388?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Kessler updated CXF-7388:
-------------------------------
    Attachment: cxf.client.test.sync.junit.ext.zip

> Problem with MTOM in Camel-CXF
> ------------------------------
>
>                 Key: CXF-7388
>                 URL: https://issues.apache.org/jira/browse/CXF-7388
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.1.9
>            Reporter: Joerg Kessler
>             Fix For: 3.2.0
>
>         Attachments: cxf.client.test.sync.junit.ext.zip
>
>
> Hi,
> I posted this on the CXF user list without getting a response (except fro=
m Aki who supports this);
> We use CXF 3.1.9 together with Camel 2.17.4. We want to enable MTOM on th=
e Camel-CXF producer. To test it I created a simple route using Camel test =
infrastructure where the producer uses a WSDL with base64 encoded payload p=
arts. But in the log output of CXF I always get a payload like this
> Http-Method: POST
> Content-Type: multipart/related; type=3D"application/xop+xml"; boundary=
=3D"uuid:2a84a041-d9ce-4caf-a8e1-b4247e1ad6d6"; start=3D"<root.message@cxf.=
apache.org>"; start-info=3D"text/xml"
> Headers: {Accept=3D[*/*], breadcrumbId=3D[ID-WDFN32392889A-65347-14948506=
21554-0-1], Cache-Control=3D[no-cache], connection=3D[keep-alive], Content-=
Length=3D[487], content-type=3D[multipart/related; type=3D"application/xop+=
xml"; boundary=3D"uuid:2a84a041-d9ce-4caf-a8e1-b4247e1ad6d6"; start=3D"<roo=
t.message@cxf.apache.org>"; start-info=3D"text/xml"], Host=3D[localhost:877=
0], Pragma=3D[no-cache], SOAPAction=3D[""], User-Agent=3D[Apache-CXF/3.1.9]=
}
> Payload: --uuid:2a84a041-d9ce-4caf-a8e1-b4247e1ad6d6
> Content-Type: application/xop+xml; charset=3DUTF-8; type=3D"text/xml"
> Content-Transfer-Encoding: binary
> Content-ID: <root.message@cxf.apache.org>
> <soap:Envelope xmlns:soap=3D"http://schemas.xmlsoap.org/soap/envelope/"><=
soap:Body><typ:testXop xmlns:typ=3D"http://cxf.apache.org/mime/types"><typ:=
name>?</typ:name><typ:attachinfo>U1VDQ0VTUw=3D=3D</typ:attachinfo></typ:tes=
tXop></soap:Body></soap:Envelope>
> --uuid:2a84a041-d9ce-4caf-a8e1-b4247e1ad6d6--
> This is not MTOM. The endpoint configuration is
>     <cxf:cxfEndpoint id=3D"clientEndpoint" address=3D"http://localhost:87=
70/cxf/mtom" bus=3D"ClientBus" wsdlURL=3D"wsdl/mtom_xop.wsdl">
>         <cxf:properties>
>             <entry key=3D"dataFormat" value=3D"PAYLOAD" />
>             <entry key=3D"defaultOperationName" value=3D"testXop" />
>             <entry key=3D"defaultOperationNamespace" value=3D"http://cxf.=
apache.org/mime"/>
>             <entry key=3D"mtom-enabled" value=3D"true" />
>         </cxf:properties>
>     </cxf:cxfEndpoint>
> Here I even used a WSDL that is used in the CXF MTOM tests. Then I compar=
ed the execution of the relevant interceptors in Camel-CXF and CXF and foun=
d one difference:
> In AbstractOutDatabindingInterceptor. writeToOutputStream() it is checked=
 that the data binding is implemented by the class org.apache.cxf.jaxb.JAXB=
DataBinding. That is correct for CXF but Camel-CXF sets in CxfEndpoint the =
 binding to org.apache.camel.component.cxf.HybridSourceDataBinding which is=
 derived from JAXBDataBinding but of course is a different class. This seem=
s to prevent the completion of the MTOM conversion. I changed the code loca=
lly so that now all subclasses are accepted and now the attachment processi=
ng gets really called. But now the next problem apears; HybridSourceDataBin=
ding.createWriter() raises an exception:
> java.lang.UnsupportedOperationException: The type java.io.OutputStream is=
 not supported.
> =09at org.apache.camel.component.cxf.HybridSourceDataBinding.createWriter=
(HybridSourceDataBinding.java:87)
> I guess the method getSupportedWriterFormats of JAXBDataBinding/HybridSou=
rceDataBinding should prevent something like this but in this case it does =
not work.
> I am also unsure whether the problem is now really in CXF or in Camel-CXF=
. Therefore please forward it to Camel if the problem is locarted there.=20
> Best Regards,
> J=C3=B6rg


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)