Hi, Thank you for the reply.
We are dynamically setting the CXF endpoint address using the header "CamelDestinationOverrideUrl", as this address is coming from the message payload. Therefore, in CXF bean definition, the address is "http://dummy";. I will try the latest Camel version. The general problem for upgrading is that we will need to perform a lot of reggression tests and probably some minor changes to our existing services to work the exact same way. Igor -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CXF-synchronous-true-setting-causes-CXF-bean-invocation-last-for-60-seconds-or-more-tp5716160p5716186.html Sent from the Camel - Users mailing list archive at Nabble.com.
