You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Marcin Gałązka (JIRA)" <ji...@apache.org> on 2008/07/18 09:40:32 UTC
[jira] Created: (CXF-1706) Aegis binding behaves differently than
JAXB in regards to MTOM support
Aegis binding behaves differently than JAXB in regards to MTOM support
----------------------------------------------------------------------
Key: CXF-1706
URL: https://issues.apache.org/jira/browse/CXF-1706
Project: CXF
Issue Type: Improvement
Components: Aegis Databinding
Affects Versions: 2.1.1
Reporter: Marcin Gałązka
There are few differences in an MTOM support between Aegis and JAXB, which can be potentially confusing.
a) JAXB always accepts a XOP request, Aegis only if an MTOM is enabled
b) Aegis can't handle a DataHandler if an MTOM is not enabled (the same as a?)
c) to handle a DataHandler on method parameters it is enough to enable an MTOM using AegisDataBinding#setMtomEnabled(), but to handle a DataHandler as a return value you must additionally enable an MTOM via jaxws:properties
Maybe enabling an MTOM via jaxw:properties or an annotation should be automatically propagated to Aegis (no need to use AegisDataBinding#setMtomEnabled()). There are one gotcha here I think - jaxws:properties are defined per service, AegisDataBinding instance can be shared between many services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1706) Aegis binding behaves differently than
JAXB in regards to MTOM support
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies resolved CXF-1706.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3
r831611
Most of this was fixed some time ago. The only bit I had to change was to make Base64 accept MTOM even when the flag is not turned on. The rest of this was apparently dealt with in the 2.2 refactoring.
> Aegis binding behaves differently than JAXB in regards to MTOM support
> ----------------------------------------------------------------------
>
> Key: CXF-1706
> URL: https://issues.apache.org/jira/browse/CXF-1706
> Project: CXF
> Issue Type: Improvement
> Components: Aegis Databinding
> Affects Versions: 2.1.1
> Reporter: Marcin Gałązka
> Assignee: Benson Margulies
> Fix For: 2.3
>
>
> There are few differences in an MTOM support between Aegis and JAXB, which can be potentially confusing.
> a) JAXB always accepts a XOP request, Aegis only if an MTOM is enabled
> b) Aegis can't handle a DataHandler if an MTOM is not enabled (the same as a?)
> c) to handle a DataHandler on method parameters it is enough to enable an MTOM using AegisDataBinding#setMtomEnabled(), but to handle a DataHandler as a return value you must additionally enable an MTOM via jaxws:properties
> Maybe enabling an MTOM via jaxw:properties or an annotation should be automatically propagated to Aegis (no need to use AegisDataBinding#setMtomEnabled()). There are one gotcha here I think - jaxws:properties are defined per service, AegisDataBinding instance can be shared between many services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1706) Aegis binding behaves differently than
JAXB in regards to MTOM support
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1706:
-----------------------------
Fix Version/s: (was: 2.3)
2.2.5
> Aegis binding behaves differently than JAXB in regards to MTOM support
> ----------------------------------------------------------------------
>
> Key: CXF-1706
> URL: https://issues.apache.org/jira/browse/CXF-1706
> Project: CXF
> Issue Type: Improvement
> Components: Aegis Databinding
> Affects Versions: 2.1.1
> Reporter: Marcin Gałązka
> Assignee: Benson Margulies
> Fix For: 2.2.5
>
>
> There are few differences in an MTOM support between Aegis and JAXB, which can be potentially confusing.
> a) JAXB always accepts a XOP request, Aegis only if an MTOM is enabled
> b) Aegis can't handle a DataHandler if an MTOM is not enabled (the same as a?)
> c) to handle a DataHandler on method parameters it is enough to enable an MTOM using AegisDataBinding#setMtomEnabled(), but to handle a DataHandler as a return value you must additionally enable an MTOM via jaxws:properties
> Maybe enabling an MTOM via jaxw:properties or an annotation should be automatically propagated to Aegis (no need to use AegisDataBinding#setMtomEnabled()). There are one gotcha here I think - jaxws:properties are defined per service, AegisDataBinding instance can be shared between many services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1706) Aegis binding behaves differently than
JAXB in regards to MTOM support
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies reassigned CXF-1706:
-------------------------------------
Assignee: Benson Margulies
> Aegis binding behaves differently than JAXB in regards to MTOM support
> ----------------------------------------------------------------------
>
> Key: CXF-1706
> URL: https://issues.apache.org/jira/browse/CXF-1706
> Project: CXF
> Issue Type: Improvement
> Components: Aegis Databinding
> Affects Versions: 2.1.1
> Reporter: Marcin Gałązka
> Assignee: Benson Margulies
>
> There are few differences in an MTOM support between Aegis and JAXB, which can be potentially confusing.
> a) JAXB always accepts a XOP request, Aegis only if an MTOM is enabled
> b) Aegis can't handle a DataHandler if an MTOM is not enabled (the same as a?)
> c) to handle a DataHandler on method parameters it is enough to enable an MTOM using AegisDataBinding#setMtomEnabled(), but to handle a DataHandler as a return value you must additionally enable an MTOM via jaxws:properties
> Maybe enabling an MTOM via jaxw:properties or an annotation should be automatically propagated to Aegis (no need to use AegisDataBinding#setMtomEnabled()). There are one gotcha here I think - jaxws:properties are defined per service, AegisDataBinding instance can be shared between many services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.