cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <>
Subject [jira] Assigned: (CXF-1706) Aegis binding behaves differently than JAXB in regards to MTOM support
Date Sat, 17 Oct 2009 21:17:31 GMT


Benson Margulies reassigned CXF-1706:

    Assignee: Benson Margulies

> Aegis binding behaves differently than JAXB in regards to MTOM support
> ----------------------------------------------------------------------
>                 Key: CXF-1706
>                 URL:
>             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
> 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.

View raw message