You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Dirk Mahler (JIRA)" <ji...@apache.org> on 2008/09/19 10:50:52 UTC
[jira] Created: (SM-1585) CXF-SE/JSR181 client proxies should
support MTOM/attachments
CXF-SE/JSR181 client proxies should support MTOM/attachments
------------------------------------------------------------
Key: SM-1585
URL: https://issues.apache.org/activemq/browse/SM-1585
Project: ServiceMix
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.
[jira] Commented: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51167#action_51167 ]
Freeman Fang commented on SMXCOMP-32:
-------------------------------------
commit fix
http://svn.apache.org/viewvc?rev=764663&view=rev for 3.2 branch
> 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
> 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.
[jira] Commented: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51165#action_51165 ]
Freeman Fang commented on SMXCOMP-32:
-------------------------------------
need address https://issues.apache.org/jira/browse/CXF-2169 first
> 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
> 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.
[jira] Updated: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "wonko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
wonko updated SMXCOMP-32:
-------------------------
Attachment: test-case_cxfse-proxy_mtom-fail.zip
test-case for this issue. See the readme to run.
> 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
> 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.
[jira] Updated: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SMXCOMP-32:
-----------------------------------
Assignee: Freeman Fang
> 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
> 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.
[jira] Updated: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated SMXCOMP-32:
--------------------------------
Component/s: (was: servicemix-jsr181)
servicemix-cxf-bc
> 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-bc, servicemix-cxf-se
> 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.
[jira] Work started: (SMXCOMP-32) CXF-SE client proxies should
support MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SMXCOMP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMXCOMP-32 started by Freeman Fang.
> 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
> 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.
[jira] Resolved: (SMXCOMP-32) CXF-SE client proxies should support
MTOM/attachments
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ 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.