The document compares CXF proxy and CXF JaxWS configurations in Mule. With CXF proxy, the full SOAP message is passed through the flow and you see the entire XML payload in the logs. With CXF JaxWS, the SOAP envelope is unwrapped and you only see the object payload in the logs rather than the full XML. Running sample configurations and hitting endpoints with a sample SOAP request demonstrates this difference visually in the logs.

2. Difference between CXF proxy and CXF JaxWS
Based on the following configuration:
<flowname="Proxy">
<http:inbound-
endpointaddress="http://localhost:9000/proxy"exchange-
pattern="request-response"/>
<cxf:proxy-service/>
<processor-chain>
<cxf:proxy-client/>
<http:outbound-
endpointaddress="http://localhost:63081/hello"exchange-
pattern="request-response"/>
<object-to-string-transformer/>
<loggerlevel="WARN"message="After proxy: #[payload]"/>
</processor-chain>
</flow>

3. <flowname="JaxWs">
<http:inbound-
endpointaddress="http://localhost:9000/jaxws"exchange-
pattern="request-response">
<cxf:jaxws-serviceserviceClass="org.example.HelloWorld"/>
</http:inbound-endpoint>
<set-variablevalue="helloString"variableName="method"/>
<processor-chain>
<cxf:jaxws-
clientserviceClass="org.example.HelloWorld"operation="helloStr
ing"/>
<http:outbound-
endpointaddress="http://localhost:63081/hello"exchange-
pattern="request-response"/>
</processor-chain>
<loggerlevel="WARN"message="After jaxws: #[payload]"/>
</flow>

4. <flowname="ActualService">
<http:inbound-
endpointaddress="http://localhost:63081/hello" exchange-
pattern="request-response">
<cxf:jaxws-serviceserviceClass="org.example.HelloWorld" />
</http:inbound-endpoint>
<set-payloadvalue="the payload"/>
</flow>
In order to see the differences, please do the following:
1. Run the above configuration
2. Hit the endpoint http://localhost:9000/proxy with below SOAP message:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:exam="http://example.org/">
<soapenv:Header/>
<soapenv:Body>
<exam:helloString>
<arg0>?</arg0>
</exam:helloString>
</soapenv:Body>
</soapenv:Envelope>

5. 1. Check the logs and you will see the below line. As you can see you have the whole
SOAP message after the CXF call:
11458[connector.http.mule.default.receiver.03]WARN (LoggerMessageProcessor.ja
va:98) -After proxy:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body><ns2:helloStringResponse xmlns:ns2="http://example.org/">
<return>the payload</return></ns2:helloStringResponse>
</soap:Body></soap:Envelope>
2. Now hit the endpoint http://localhost:9000/jaxws with the same SOAP message as in
step 2.
3. Check the logs and now you will see the payload of the response:
8803[connector.http.mule.default.receiver.03]WARN (LoggerMessageProcessor.jav
a:98) -After jaxws: the payload
As you can observe from the logs, when you are using Proxy you are getting the
full SOAP message while when using JaxWs you get the object part of response.