Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 30 May 2017 04:49:04 +0000 (UTC)
From: "Joerg Kessler (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.13075736.1496119737000.317316.1496119744168@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] [Created] (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 04:49:10 -0000

Joerg Kessler created CXF-7388:
----------------------------------

             Summary: Problem with MTOM in Camel-CXF
                 Key: CXF-7388
                 URL: https://issues.apache.org/jira/browse/CXF-7388
             Project: CXF
          Issue Type: Bug
            Reporter: Joerg Kessler


Hi,
I posted this on the CXF user list without getting a response (except from =
Aki who supports this);
We use CXF 3.1.9 together with Camel 2.17.4. We want to enable MTOM on the =
Camel-CXF producer. To test it I created a simple route using Camel test in=
frastructure where the producer uses a WSDL with base64 encoded payload par=
ts. 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.apac=
he.org>"; start-info=3D"text/xml"
Headers: {Accept=3D[*/*], breadcrumbId=3D[ID-WDFN32392889A-65347-1494850621=
554-0-1], Cache-Control=3D[no-cache], connection=3D[keep-alive], Content-Le=
ngth=3D[487], content-type=3D[multipart/related; type=3D"application/xop+xm=
l"; boundary=3D"uuid:2a84a041-d9ce-4caf-a8e1-b4247e1ad6d6"; start=3D"<root.=
message@cxf.apache.org>"; start-info=3D"text/xml"], Host=3D[localhost:8770]=
, 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/"><so=
ap:Body><typ:testXop xmlns:typ=3D"http://cxf.apache.org/mime/types"><typ:na=
me>?</typ:name><typ:attachinfo>U1VDQ0VTUw=3D=3D</typ:attachinfo></typ:testX=
op></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:8770=
/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.ap=
ache.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 compared=
 the execution of the relevant interceptors in Camel-CXF and CXF and found =
one difference:
In AbstractOutDatabindingInterceptor. writeToOutputStream() it is checked t=
hat the data binding is implemented by the class org.apache.cxf.jaxb.JAXBDa=
taBinding. That is correct for CXF but Camel-CXF sets in CxfEndpoint the  b=
inding to org.apache.camel.component.cxf.HybridSourceDataBinding which is d=
erived from JAXBDataBinding but of course is a different class. This seems =
to prevent the completion of the MTOM conversion. I changed the code locall=
y so that now all subclasses are accepted and now the attachment processing=
 gets really called. But now the next problem apears; HybridSourceDataBindi=
ng.createWriter() raises an exception:
java.lang.UnsupportedOperationException: The type java.io.OutputStream is n=
ot supported.
=09at org.apache.camel.component.cxf.HybridSourceDataBinding.createWriter(H=
ybridSourceDataBinding.java:87)
I guess the method getSupportedWriterFormats of JAXBDataBinding/HybridSourc=
eDataBinding should prevent something like this but in this case it does no=
t 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)