Return-Path: 
 <users-return-10815-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 54009 invoked from network); 11 Jan 2010 14:49:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 11 Jan 2010 14:49:31 -0000
Received: (qmail 44336 invoked by uid 500); 11 Jan 2010 14:49:31 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 44280 invoked by uid 500); 11 Jan 2010 14:49:31 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 44270 invoked by uid 99); 11 Jan 2010 14:49:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 14:49:31 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 209.85.220.218 as permitted sender)
Received: from [209.85.220.218] (HELO mail-fx0-f218.google.com)
 (209.85.220.218)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jan 2010 14:49:22 +0000
Received: by fxm10 with SMTP id 10so7888167fxm.34
        for <users@camel.apache.org>; Mon, 11 Jan 2010 06:49:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :from:date:message-id:subject:to:content-type;
        bh=EP0qhzjCZDnuY2YVNZjCdvKm/hSAc+DvOWsJorE2V84=;
        b=QGGLDqDfNdgj/c4GYvPm/Od9Vj+58Q3kGN760U56j7n5vlR8vxc70XtJM12GgjhO21
         hm0TwqYLWMKWpK7i69rOIMgU4R+lJYfbxEmqxy7eBW9zPOlQdLCHNE/gOyWkWNeAeGl5
         lyZvISG8W+Jv0WA5nLZqSRs2WdMtkwE3meti4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=lqv2BLHoL/ABH2YLeNiEH97Sf/OEne7STY5akRVKuNhYMaYSvFMEbY4l0oBPNzxR6+
         t6Kq/2/pICEl/VxwUGQ/wyF1QFQguVxS0o/1WuGhePLV1RjQt97z2+xGC+zNLbxe5cfW
         w+euJHxsAIWPWlpbQkB00/AGVOVmi1w7Livo8=
MIME-Version: 1.0
Received: by 10.239.185.77 with SMTP id b13mr1243609hbh.158.1263221341105;
	Mon, 11 Jan 2010 06:49:01 -0800 (PST)
In-Reply-To: <27111395.post@talk.nabble.com>
References: <27107483.post@talk.nabble.com>
 <5380c69c1001110106y75f69d45h2b1dd14076df890d@mail.gmail.com>
	<27107783.post@talk.nabble.com>
 <5380c69c1001110222t1a4fcd0bwf1e7d8feece6a11e@mail.gmail.com>
	<27108985.post@talk.nabble.com>
 <5380c69c1001110329pac26ad2j986978587225e533@mail.gmail.com>
	<27109901.post@talk.nabble.com>
 <ec6e67fd1001110629i54c5a718v3d20c8b8b859f2e7@mail.gmail.com>
	<27111395.post@talk.nabble.com>
From: James Strachan <james.strachan@gmail.com>
Date: Mon, 11 Jan 2010 14:48:41 +0000
Message-ID: <ec6e67fd1001110648w3705e6ddu5e6a64feb622ae7f@mail.gmail.com>
Subject: Re: route debugging
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

2010/1/11 yaog <yairogen@gmail.com>:
>
> Basically, I am evaluating Camel at the moment.
>
> It is desired by our architecture to have routes that activate different
> beans (through different queues) and be able to get their responses back to
> the caller thread.

So to activate your two beans when a message is sent to queue "compA"
or "compB" you'd write 2 routes like this...

<route>
  <from uri="jms:compA" />
  <to uri="bean:compAImpl" />
</route>
<route>
  <from uri="jms:compB" />
  <to uri="bean:compBImpl" />
</route>

Each route represents a 'consumer' on a queue. In this case you are
creating 2 consumers on queues compA and compB which when a message is
sent to them, you invoke beans and return the response.


The single route with a single pipeline you started this thread with
has a different effect...

   <route id="route1">
                       <from uri="direct:start" />
                       <to uri="bean:compAImpl" />
                       <to uri="jms:compB" />
                       <to uri="bean:compBImpl" />
                       <to uri="jms:compC" />
                       <to uri="bean:compCImpl" />
               </route>

this will just send a message to compB queue (i.e be a producer on
that queue, not a consumer) and wait for the response from that queue,
then send it on to the bean compBImpl. i.e. for the pipeline to work,
there must be a consumer on the queue compB. This is why Claus
suggested a separate route to act as the consumer on queue compB.


> So that is what I am trying to do. If I define different routes I will not
> be able to send the info back...

I don't follow this last sentence.



-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/