[
https://issues.apache.org/jira/browse/CXF-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated CXF-4987:
-------------------------------------
Fix Version/s: 2.6.11
2.7.8
> org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor disables mtom silently
> ---------------------------------------------------------------------------
>
> Key: CXF-4987
> URL: https://issues.apache.org/jira/browse/CXF-4987
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.7.4
> Reporter: Stefan Magnus Landrø
> Labels: mtom, security
> Fix For: 2.7.8, 2.6.11
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> handleMessage(..) in WSS4JOutInterceptor disables mtom silently:
> public void handleMessage(SoapMessage mc) throws Fault {
> //must turn off mtom when using WS-Sec so binary is inlined so it can
> //be properly signed/encrypted/etc...
> if (!mtomEnabled) {
> mc.put(org.apache.cxf.message.Message.MTOM_ENABLED, false);
> }
>
> ....
> }
> It would make sense to add a log warning if the client is configured to use
> mtom and the WSS4JInterceptor:
> public void handleMessage(SoapMessage mc) throws Fault {
> //must turn off mtom when using WS-Sec so binary is inlined so it can
> //be properly signed/encrypted/etc...
> if(mc.get(org.apache.cxf.message.Message.MTOM_ENABLED) == true &&
> !mtomEnabled) {
> log.warn("Incomatible configurations .... bla bla bla");
> }
> if (!mtomEnabled) {
> mc.put(org.apache.cxf.message.Message.MTOM_ENABLED, false);
> }
>
> ....
> }
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
