camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From El Bennitto <david.benni...@metapack.com>
Subject CXF PAYLOAD SOAPAction not set using WSDL
Date Mon, 16 May 2016 13:56:11 GMT
The Camel CXF doc states:-

"If the wsdlURL option is provided, serviceClass is not required for PAYLOAD
and MESSAGE mode. When wsdlURL option is used without serviceClass, the
serviceName and portName (endpointName for Spring configuration) options
MUST be provided."
 
 Using Camel: 2.17.1 I have configured my CXF endpoint for PAYLOAD mode as
follows:-
 

 
 However, when the web service is called it returns:-



I can see in the request log that the SOAPAction header is not set.
 
 If I configure the URI to use the serviceClass and remove the wsdlURL,
serviceName and endpointName (but still with a dataFormat of PAYLOAD) as
below then the SOAPAction is set and the web service is called successfully. 
 

 
 So it appears to be able to get the SOAPAction from the ServiceClass but
not the WSDL. Although this works for me, it means that I am having to
include the web service Java bindings just to get the SOAPAction populated
when I shouldn't need them at all.
 
 I can see from  https://issues.apache.org/jira/browse/CAMEL-7921 that there
have been problems in the past in this area but perhaps I have just
misconfigured my URI.
 
 The full WSDL can be found here:
http://api.channeladvisor.com/ChannelAdvisorAPI/v7/OrderService.asmx?wsdl
 
 WSDL Binding and Service definitions:-
 david.bennison@metapack.com



--
View this message in context: http://camel.465427.n5.nabble.com/CXF-PAYLOAD-SOAPAction-not-set-using-WSDL-tp5782671.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message