Hi!
I'm using Camel 2.15.0 and the CXF component (CXF 3.0.4) to call a SOAP 1.2
web service in PAYLOAD mode. The call in itself works fine, however
necessary out of band soap headers (i.e. not defined in the contract) are
not relayed to the service endpoint for some reason.
In the log I can see the following trace message :
TRACE org.apache.camel.component.cxf.DefaultCxfBinding - Propagate
SOAP/protocol header:
{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
: [wsse:Security: null]
But at the server side all I get are the typical SOAP 1.2 addressing headers
(Action, ReplyTo etc) which the cxf component seems to have generated for
me, and all the other soap headers are gone. I've used wireshark to
determine that the problem seem to be in the CXF consumer somewhere.
I have a similar use case calling a SOAP 1.1 web service and there soap
header relaying works fine.
Any ideas why the soap headers aren't relayed in my cxf client?
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-headers-not-relayed-for-a-SOAP-1-2-service-when-using-CXF-component-tp5765823.html
Sent from the Camel - Users mailing list archive at Nabble.com.
