Re: SOAP headers not relayed for a SOAP 1.2 service when using CXF component
No further comments? :) -- 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-tp5765823p5765987.html Sent from the Camel - Users mailing list archive at Nabble.com.
SOAP headers not relayed for a SOAP 1.2 service when using CXF component
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.
Re: SOAP headers not relayed for a SOAP 1.2 service when using CXF component
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.wsdldataFormat=PAYLOADendpointName={urn:test:namespace}MyServiceSOAPserviceName={urn:test:namespace}MyServiceskipFaultLogging=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.
Re: SOAP headers not relayed for a SOAP 1.2 service when using CXF component
How did you specify the SOAP 1.2 binding in your camel-cxf endpoint?
What kind of soap header were lost?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On April 15, 2015 at 9:28:44 PM, _redwings (eriknygre...@gmail.com) wrote:
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.
