Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 18 Mar 2014 20:44:43 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12694968.1392294200409.99935.1395175483701@arcas>
In-Reply-To: <JIRA.12694968.1392294200409@arcas>
References: <JIRA.12694968.1392294200409@arcas>
Subject: [jira] [Resolved] (CXF-5560) MTOM does not work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Daniel Kulp resolved CXF-5560.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


See discussion in thread:=20

http://cxf.547215.n5.nabble.com/Query-on-CXF-dispatch-client-with-MTOM-tp57=
39745p5740537.html

> MTOM does not work
> ------------------
>
>                 Key: CXF-5560
>                 URL: https://issues.apache.org/jira/browse/CXF-5560
>             Project: CXF
>          Issue Type: Bug
>         Environment: I am using CXF 3.0.0 milestone 1
>            Reporter: Alekhya Gumudavelli
>            Assignee: Daniel Kulp
>            Priority: Critical
>             Fix For: Invalid
>
>
> CXF forums claim that  MTOM can be enabled by setting MTOMenabled propert=
y to true.=20
>      ((SOAPBinding)binding).setMTOMEnabled(true);
> This alone is not inserting an xop include element on the base64 element.=
 We need a node level optimization mechanism like we do in axis2. We could =
not find any such equivalent in CXF.=20
> We have gone through CXF code and found that AttachmentOutInterceptor use=
s MTOM enabled property to set content-type to =E2=80=9Capplication/xop+xml=
=E2=80=9D but it does not have any other optimization logic or include xop =
href element.


--
This message was sent by Atlassian JIRA
(v6.2#6252)