I also noticed that the message appears twice in the target queue.
-----Original Message----- From: Jos Dirksen [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 2:06 PM To: [email protected] Subject: Re: Receipient *List* seems not to work in Camel 1.2.0 I'm experiencing the same problem. With the 1.2.0 release and also with the latest from SVN. One way or the other the last route is always used. private final static String ENDPOINT_1 = "jbi:endpoint:http://servicemix.apache.org/samples/filemover/fileSender/ fileSenderEndpoint"; private final static String ENDPOINT_2 = "jbi:endpoint:http://servicemix.apache.org/samples/filemover/anotherFile Sender/anotherFileSenderEndpoint"; public void configure() throws Exception { from("jbi:service:http://servicemix.apache.org/samples/filemover/camelRe ceiver").to(ENDPOINT_1,ENDPOINT_2); } Very simple route, however instead of sending it once to endpoint_1 it get's sent twice to endpoint_2. I've been debugging a bit and to problem seem to occur in the " wrapProcessorInInterceptors(RouteContext routeContext, Processor target)" method of the ProcessorType class. To be more specific, I can see my old routes being overwritten in this part of the method: for (InterceptorType interceptorRef : interceptors) { DelegateProcessor p = interceptorRef.createInterceptor(routeContext); if (first == null) { first = p; } if (last != null) { last.setProcessor(p); } last = p; } if (last != null) { last.setProcessor(target); } Andreas G Guther wrote: > > Either I am getting something wrong or the current 1.2.0 version has > some problems. > -- View this message in context: http://www.nabble.com/Receipient-*List*-seems-not-to-work-in-Camel-1.2.0 -tf4596679s22882.html#a13124770 Sent from the Camel - Users mailing list archive at Nabble.com.
