Return-Path: 
 <users-return-17846-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 7442 invoked from network); 19 Jan 2011 13:23:35 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 19 Jan 2011 13:23:35 -0000
Received: (qmail 50474 invoked by uid 500); 19 Jan 2011 13:23:35 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 50303 invoked by uid 500); 19 Jan 2011 13:23:33 -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 50286 invoked by uid 99); 19 Jan 2011 13:23:31 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jan 2011 13:23:31 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [193.61.220.150] (HELO magi.llgc.org.uk) (193.61.220.150)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jan 2011 13:23:22 +0000
Received: from p597xp.wyddfa.llgc.org.uk ([193.61.222.12])
	by magi.llgc.org.uk with esmtp (Exim 4.63)
	(envelope-from <rem@llgc.org.uk>)
	id 1PfY06-0008D8-C6
	for users@camel.apache.org; Wed, 19 Jan 2011 13:23:02 +0000
Message-ID: <4D36E583.4070100@llgc.org.uk>
Date: Wed, 19 Jan 2011 13:22:11 +0000
From: Remi Malessa <rem@llgc.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc13 Thunderbird/3.1.7
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: <handled/>
References: <1295347251916-3345975.post@n5.nabble.com>
 <AANLkTinu7ZXwPQAm=bNd8e_ZQxBH7ctyvG6=BtWm-H-6@mail.gmail.com>
 <1295351137217-3346058.post@n5.nabble.com> <4D35AFC7.5050402@llgc.org.uk>
 <AANLkTikH2vHHMzk8V6u25grhxDdipHfKpFGmJW=8rcxz@mail.gmail.com>
 <3749A89E-DE2C-4B4D-BADD-92898F97BBE7@gmail.com>
 <4D36BDA7.8090402@llgc.org.uk>
 <AANLkTikPkQsbp=N_bQP3SA66arzV+T=daS64w1DwLEbZ@mail.gmail.com>
In-Reply-To: <AANLkTikPkQsbp=N_bQP3SA66arzV+T=daS64w1DwLEbZ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

On 01/19/2011 10:45 AM, Claus Ibsen wrote:
> See figure 5.5. When handled=true, the caused exception will be
> removed from the exchange, and the route consumer will not "detect"
> any exceptions caused processing the exchange.
>
> When handled=false, the caused exception will be placed on the
> exchange, and the route consumer will "detect" the exception and can
> react for example by rolling back. This is consumer specific what
> action they do on detecting an exception.
Alright, so if there is no handle=true and no exception handling 
implemented in the
consumer, it can even skip/ignore the message ?

Remi