Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 85343 invoked from network); 12 May 2008 08:38:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 May 2008 08:38:26 -0000 Received: (qmail 5195 invoked by uid 500); 12 May 2008 08:38:28 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 5179 invoked by uid 500); 12 May 2008 08:38:28 -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 5168 invoked by uid 99); 12 May 2008 08:38:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 May 2008 01:38:28 -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; Mon, 12 May 2008 08:37:41 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JvTXf-0002tw-Hf for camel-user@activemq.apache.org; Mon, 12 May 2008 01:37:55 -0700 Message-ID: <17183442.post@talk.nabble.com> Date: Mon, 12 May 2008 01:37:55 -0700 (PDT) From: rzfrantz To: camel-user@activemq.apache.org Subject: Exchanges, MEP and Exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: rzfrantz@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hi all! In a communication between 2 endpoints, if the consumer at the destination endpoint raise an exception, it could add a fault message to the Exchange and then send the Exchange back to the source endpoint, right? But what happens if one task, for example a filter task, raise an exception during its execution in the middle of the route? How does this filter task can inform the source endpoint? Thanks a lot, Rafael. -- View this message in context: http://www.nabble.com/Exchanges%2C-MEP-and-Exceptions-tp17183442s22882p17183442.html Sent from the Camel - Users mailing list archive at Nabble.com.