You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Stefan Magnus Landrø (JIRA)" <ji...@apache.org> on 2013/04/25 15:06:15 UTC

[jira] [Created] (CXF-4987) org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor disables mtom silently

Stefan Magnus Landrø created CXF-4987:
-----------------------------------------

             Summary: 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ø


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira