Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 54295 invoked from network); 8 Jul 2008 07:05:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jul 2008 07:05:14 -0000 Received: (qmail 72350 invoked by uid 500); 8 Jul 2008 07:05:14 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 72335 invoked by uid 500); 8 Jul 2008 07:05:14 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 72324 invoked by uid 99); 8 Jul 2008 07:05:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2008 00:05:14 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2008 07:04:21 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KG7Fi-0001sS-Ue for camel-user@activemq.apache.org; Tue, 08 Jul 2008 00:04:42 -0700 Message-ID: <18333101.post@talk.nabble.com> Date: Tue, 8 Jul 2008 00:04:42 -0700 (PDT) From: cmoulliard To: camel-user@activemq.apache.org Subject: Re: route definition: component response routing In-Reply-To: <594203920807011823i63f2d192vfdd4de81de03fded@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: cmoulliard@gmail.com References: <594203920806291447x7f717cdfm71421845882e721b@mail.gmail.com> <594203920807011823i63f2d192vfdd4de81de03fded@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi Vlad, If the destination endpoint is not defined, an error will be generated when your message will be send. Different strategies exist to avoid to lost your message in this situation : - Implement a DeadLetterchannel, - Define your "from" endpoint as a transactional endpoint to provide a rollback Regards, Charles volenin wrote: > > Does anyone have any suggestion re: this question?... > > > On Sun, Jun 29, 2008 at 5:47 PM, Vlad Olenin wrote: > >> Hi, >> >> I was browsing through the documentation recently trying to find the >> answer >> for the following question. If the outbound route from one of the >> endpoints >> is not defined, does it mean that the response that component is creating >> would be propagated back through the request chain? Or it would just >> terminate on that endpoint? In other words, does Camel behavior in this >> case >> resembles that of Mule or not? (From what I read, in Mule if the outbound >> route is not defined, the message would 'bounce back' along the >> invocation >> chain towards the original caller). >> >> Thanks, >> >> Vlad >> > > -- View this message in context: http://www.nabble.com/route-definition%3A-component-response-routing-tp18185736s22882p18333101.html Sent from the Camel - Users mailing list archive at Nabble.com.