You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/11/14 14:17:26 UTC

[jira] Resolved: (CAMEL-170) FW: Receipient *List* seems not to work in Camel 1.2.0

     [ https://issues.apache.org/activemq/browse/CAMEL-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved CAMEL-170.
----------------------------------

    Resolution: Cannot Reproduce

Until we figure out how to reproduce this issue, I'm gonna mark it as cannot reproduce - let us know if you can find a way to reproduce and we can reopen

> FW: Receipient *List* seems not to work in Camel 1.2.0
> ------------------------------------------------------
>
>                 Key: CAMEL-170
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-170
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Andreas Guther
>
> -----Original Message-----
> From: Jos Dirksen [mailto:jos.dirksen@gmail.com] 
> Sent: Tuesday, October 09, 2007 2:06 PM
> To: camel-user@activemq.apache.org
> 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/anotherFileSender/anotherFileSenderEndpoint";
>     
>     public void configure() throws Exception {
>        
> from("jbi:service:http://servicemix.apache.org/samples/filemover/camelReceiver").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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.