[ 
https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved SMXCOMP-32.
---------------------------------

       Resolution: Fixed
    Fix Version/s: servicemix-cxf-se-2009.02
                   servicemix-cxf-bc-2009.02
                   3.2.4

commit fix
http://svn.apache.org/viewvc?rev=765045&view=rev for servicemix-cxf-se component
http://svn.apache.org/viewvc?rev=765046&view=rev for servicemix-cxf-bc component

> CXF-SE client proxies should support MTOM/attachments
> -----------------------------------------------------
>
>                 Key: SMXCOMP-32
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-32
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-cxf-se, servicemix-jsr181
>    Affects Versions: 3.2.1
>         Environment: ServiceMix 3.2.1
> embedded deployment
>            Reporter: Dirk Mahler
>            Assignee: Freeman Fang
>             Fix For: 3.2.4, servicemix-cxf-bc-2009.02, 
> servicemix-cxf-se-2009.02
>
>         Attachments: test-case_cxfse-proxy_mtom-fail.zip
>
>
> The JSR181 and CXF-SE components both support MTOM/attachements by setting 
> the property "mtomEnabled" in the deployment configuration.  To provide a 
> consistent programming model using these componentes it would be nice if the 
> JSR181 and CXF-SE client proxies could handle binary data the same way.
> According to the XFire/CXF documentation ((http://xfire.codehaus.org/MTOM and 
> http://cwiki.apache.org/CXF20DOC/mtom-attachments.html) it is necessary to 
> set the property "mtom-enabled" on the client factory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to