[
https://issues.apache.org/jira/browse/CXF-5560?page=com.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:
http://cxf.547215.n5.nabble.com/Query-on-CXF-dispatch-client-with-MTOM-tp5739745p5740537.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 property to
> true.
> ((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.
> We have gone through CXF code and found that AttachmentOutInterceptor uses
> MTOM enabled property to set content-type to “application/xop+xml” but it
> does not have any other optimization logic or include xop href element.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
