I should have clarified what I was asking:  Is this a bug or user error? 
Should an HTTP/SOAP1.2 provider be putting the proper Content-type HTTP
header on the message?
-- 
View this message in context: 
http://www.nabble.com/servicemix-http%3A-Content-type-HTTP-Header-Causing-Fault-in-SOAP-1.2-Request-tp19545392p19556147.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to