[
https://issues.apache.org/jira/browse/CXF-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491022
]
Chris Moesel commented on CXF-593:
----------------------------------
Forgot to add the applicable namespaces you'll need for the above configs:
xmlns:wsp="http://www.w3.org/2006/07/ws-policy";
xmlns:mtom="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization";
> Support WS-MTOMPolicy
> ---------------------
>
> Key: CXF-593
> URL: https://issues.apache.org/jira/browse/CXF-593
> Project: CXF
> Issue Type: New Feature
> Components: WS-* Components
> Affects Versions: 2.0-RC
> Reporter: Chris Moesel
> Assigned To: Dan Diephouse
> Attachments: mtom-policy.patch
>
>
> It would be good to support the MTOM Policy:
> http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/
> This would allow a service to be MTOM-enabled by adding the policy to the
> endpoint like so:
> <jaxws:features>
> <wsp:Policy>
> <mtom:OptimizedMimeSerialization />
> </wsp:Policy>
> </jaxws:features>
> This should also support the wsp:Optional attribute:
> <jaxws:features>
> <wsp:Policy>
> <mtom:OptimizedMimeSerialization wsp:Optional="true"/>
> </wsp:Policy>
> </jaxws:features>
> If the wsp:Optional attribute is set, then the service optionally supports
> MTOM like so:
> 1) If the incoming message uses MTOM, respond with MTOM
> 2) If the incoming message does not use MTOM, neither should the response
> This way, one service is able to support both MTOM-enabled and
> non-MTOM-enabled clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
