cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Resolved] (CXF-5560) MTOM does not work
Date Tue, 18 Mar 2014 20:44:43 GMT


Daniel Kulp resolved CXF-5560.

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

See discussion in thread:

> MTOM does not work
> ------------------
>                 Key: CXF-5560
>                 URL:
>             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
> 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

View raw message