Hi Willem,
Another thing to note is the issue @
https://issues.apache.org/activemq/browse/CAMEL-2452 CAMEL-2452
We have recently moved to Camel 2.5 distribution and i still see:
protected void initialize() {
getOutFilter().add("content-length");
getOutFilter().add("content-type");
// Add the filter for the Generic Message header
// http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.5
getOutFilter().add("cache-control");
getOutFilter().add("connection");
getOutFilter().add("date");
getOutFilter().add("pragma");
getOutFilter().add("trailer");
getOutFilter().add("transfer-encoding");
getOutFilter().add("upgrade");
getOutFilter().add("via");
getOutFilter().add("warning");
setLowerCase(true);
As the headers are case sensitive i guess you will have to change it to
camel case as per the issue raised earlier.
Can we expect this as a patch for 2.5 release?
Best Regards,
Madhav
unmarshall wrote:
>
> Hi Willem,
>
> Thanks for your response. I always have trace on while development. For a
> producer the binding operation info are never set. A look at the source
> code for the producer confirms the same.
>
> ....
>
>
--
View this message in context:
http://camel.465427.n5.nabble.com/Calling-external-webservice-using-cxf-camel-endpoint-tp3238383p3247470.html
Sent from the Camel - Users mailing list archive at Nabble.com.
