400 Bad Request does ring a bell. We had the same problem from MuleSoft talking to WCF. The configuration needed to be changed in WCF to solve this. I guess this is the answer that is return by WCF for some unclear reason. My advice would be to analyse the differences between interception using SoapUI and Camel. Maybe the missing <?xml ... is the reason wcf fails.
-- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-Payload-mode-tp5783530p5783563.html Sent from the Camel - Users mailing list archive at Nabble.com.
