Re: CxfProducer cache problem on Camel

2013-09-06 Thread liugang594 Liu
Hi Claus: Thanks in advance. After changed to use different uri, both a1 and a2 can be printed correctly, however I found another problem, *If I stored this value into requestContext with a static kay*, then all request has the same value. for example changed CustomDefaultCxfBinding as below cl

Re: CxfProducer cache problem on Camel

2013-09-06 Thread liugang594 Liu
but it's not a bug? because all endpoint have the same CxfBinding instance even I specified individually. 2013/9/6 Claus Ibsen > Hi > > The url is the same in the endpoint(url) so you get the same instance. > And then afterwards you set the custom cxf binding. You need 2 > different urls, so it

Re: CxfProducer cache problem on Camel

2013-09-05 Thread Claus Ibsen
Hi The url is the same in the endpoint(url) so you get the same instance. And then afterwards you set the custom cxf binding. You need 2 different urls, so its 2 different endpoint instances. Or you can crate the cxf endpoints using java code, with the new constructor. On Fri, Sep 6, 2013 at 5:36

CxfProducer cache problem on Camel

2013-09-05 Thread liugang594 Liu
Hi All: I found the CxfProducer object will be cached to reuse in Camel, however this may can's suatable for any time, to make things simple, assume we have below route: class CustomDefaultCxfBinding extends DefaultCxfBinding { private String a; public CustomDefaultCxfBinding(String a) { this.a =