I'm using CXF BC provider to make a call to external web service. Target
service expects "Content-Type=text/xml" but CXF provider sends
"application/soap+xml" without regarding SOAP version which is 1.1.
I got an error:
"server found request content type to be 'application/soap+xml;
charset=UTF-8', but expected 'text/xml'."

In cxf.xml file I specified explicitly text/xml content type but it is
apparently disregarded
(<http-conf:client ContentType="text/xml" ... )
When I look into the code I see that
org.apache.servicemix.cxfbc.interceptors.JbiOutInterceptor
sets always "application/soap+xml" content type
(see fromNMSAttachments method line: message.put(Message.CONTENT_TYPE,
"application/soap+xml");)
should soap version be taken into account here?
is it a bug or should anything more be configured?
-- 
View this message in context: 
http://www.nabble.com/CXF-BC-provider-setting-wrong-content-type-for-soap-1.1--tp18610456p18610456.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to