Hi Willem, >You can override the DefaultCxfBinding by putting your custom header >into the CXF message. camel-cxf component support you to set a custom >CxfBinding from URI with the option like this "cxfBinding=#bindingName ". > >Then you don't need add other custom processor into the route.
Yes that solved the problem and is somewhat cleaner than other approaches. Another approach would be to introduce a hook to handle / manipulate message headers / exchange properties at any point, similar to the way you have a hook to filter message headers using HeaderFilterStrategy. Thanks & Regards, madhav -- View this message in context: http://camel.465427.n5.nabble.com/CfxBinding-places-custom-headers-at-different-places-tp3354431p3360995.html Sent from the Camel - Users mailing list archive at Nabble.com.
