You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2009/04/09 09:36:34 UTC

[jira] Updated: (SMXCOMP-32) CXF-SE client proxies should support MTOM/attachments

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

Freeman Fang updated SMXCOMP-32:
--------------------------------

    Summary: CXF-SE client proxies should support MTOM/attachments  (was: CXF-SE/JSR181 client proxies should support MTOM/attachments)

> 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
>
> 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.