Hi, It dependents on how you setup the client request context header. You may need to clean up the header if you don't want to the setting affect the next camel-cxf producer.
By default camel-cxf endpoint will copy the message headers from the in message to the out message, which means the client request header will still effect on the second camel-cxf endpoint. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Monday, October 29, 2012 at 11:19 AM, ravi.4indra wrote: > Also i dont have any default configuration. so the first time i set the > timeout it will remain as my default timeout for all the endpoints? > > bean(mapper,"changeTimeOut") > to(cxf://webservice1) > bean(mapper,"changeTimeOut") > to(cxf://webservice2) > > I noticed that webservice2 is using the timeout value set during the first > step. can you explain this behaviour? > > Thanks > Ravi > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Timeout-on-a-route-tp5721576p5721684.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
