Thanks for reply.
The particular header in this example is a security/saml-token. But I've
also tried adding headers according to the example here, and neither are
passed to the endpoint:
http://camel.apache.org/cxf.html
Again, all headers are passed successfully to a similar soap 1.1 endpoint.
I've configured the endpoint using the Java DSL similar to this:
.to("cxf://http://urlOfMyService?wsdlURL=wsdl/service.wsdl&dataFormat=PAYLOAD&endpointName={urn:test:namespace}MyServiceSOAP&serviceName={urn:test:namespace}MyService&skipFaultLogging=true";)
Camel/CXF figures out the correct binding from the WSDL I guess? Seems to be
correct anyway, as the actual invoking of the service works fine apart from
the lost out of band soap headers.
Soap action are set like this:
exchange.getIn().setHeader(CxfConstants.OPERATION_NAME, "query");
exchange.getIn().setHeader(CxfConstants.OPERATION_NAMESPACE,
"urn:test:namespace");
--
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-tp5765823p5765846.html
Sent from the Camel - Users mailing list archive at Nabble.com.
