You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by Alberto <ab...@inogs.it> on 2016/07/06 08:52:59 UTC

CXF component doesn't propagate SOAPAction header

Hello,

I'm using the cxf component as producer in dispatch mode as specify in�
http://camel.apache.org/cxf.html.

The endpoint:
	<cxf:cxfEndpoint id="myEndpoint" address="http://hostname/servi
ce/soap">;
		<cxf:properties>
��������	<entry key="dataFormat" value="PAYLOAD"/>
��������</cxf:properties>
	</cxf:cxfEndpoint>


The relevant part of the route:

� ��		.setHeader(SoapBindingConstants.SOAP_ACTION,
constant("urn:InsertObservation"))
����		.to("cxf:bean:myEndpoint")

Enabling debug I can see:

...
DefaultCxfBinding��������������DEBUG Propagate to CXF header:
SOAPAction value: urn:InsertObservation
...
Headers������������������������DEBUG SOAPAction: ""
..


Using wireshark I can confirm that the SOAPACtion http header is empty.


Is it a bug? Something missing?

Regards

Alberto

Re: CXF component doesn't propagate SOAPAction header

Posted by Alberto <ab...@inogs.it>.

Solved,

specify soap version 1.2 do the job.

I added the following line to the cxfEndpoint:

<cxf:binding>
	<soap:soapBinding version="1.2"/>
</cxf:binding>

Regards

Alberto



On Wed, 2016-07-06 at 10:52 +0200, Alberto wrote:
> Hello,
> 
> I'm using the cxf component as producer in dispatch mode as specify
> in�
> http://camel.apache.org/cxf.html.
> 
> The endpoint:
> 	<cxf:cxfEndpoint id="myEndpoint" address="http://hostname/servi
> ce/soap">;
> 		<cxf:properties>
> ��������	<entry key="dataFormat" value="PAYLOAD"/>
> ��������</cxf:properties>
> 	</cxf:cxfEndpoint>
> 
> 
> The relevant part of the route:
> 
> � ��		.setHeader(SoapBindingConstants.SOAP_ACTION,
> constant("urn:InsertObservation"))
> ����		.to("cxf:bean:myEndpoint")
> 
> Enabling debug I can see:
> 
> ...
> DefaultCxfBinding��������������DEBUG Propagate to CXF header:
> SOAPAction value: urn:InsertObservation
> ...
> Headers������������������������DEBUG SOAPAction: ""
> ..
> 
> 
> Using wireshark I can confirm that the SOAPACtion http header is
> empty.
> 
> 
> Is it a bug? Something missing?
> 
> Regards
> 
> Alberto