Return-Path: <users-return-62163-archive-asf-public=cust-asf.ponee.io@camel.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 1FAA5200B60
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Sun, 14 Aug 2016 18:30:00 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 1E4C0160AA9; Sun, 14 Aug 2016 16:30:00 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 8C4EB160A8B
	for <archive-asf-public@cust-asf.ponee.io>; Sun, 14 Aug 2016 18:29:59 +0200 (CEST)
Received: (qmail 75841 invoked by uid 500); 14 Aug 2016 16:29:58 -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
Delivered-To: moderator for users@camel.apache.org
Received: (qmail 59334 invoked by uid 99); 12 Aug 2016 15:02:28 -0000
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.313
X-Spam-Level: **
X-Spam-Status: No, score=2.313 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001,
	URI_HEX=1.313] autolearn=disabled
Date: Fri, 12 Aug 2016 08:02:23 -0700 (MST)
From: rburdet <rodrigo.burdet@semperti.com>
To: users@camel.apache.org
Message-ID: <1471014143068-5786363.post@n5.nabble.com>
Subject: Extrange behaviour of exceptions
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Sun, 14 Aug 2016 16:30:00 -0000

Hi. i have some doubts about the execution of these camel routes: 

        <route id="route1">
            <from uri="direct:start"/>
            <onException>
            	<exception>java.lang.Exception</exception>
           	<bean ref="exceptionUtil" method="handleException"/>
            </onException>
           <to uri="direct:invokerMainRoute"/>
           <to uri="mock:result"/>
        </route>

        <route id="route2">
            <from uri="direct:start"/>
            <onException>
            	<exception>javax.ws.rs.ServiceUnavailableException</exception>
           	<bean ref="exceptionUtil" method="handleException"/>
          </onException>
           <to uri="direct:invokerMainRoute"/>
           <to uri="mock:result"/>
        </route>

        <route id="route3">
            <from uri="direct:start"/>
            <doTry>
            	<to uri="direct:invokerMainRoute"/>
            	<to uri="mock:result"/>
            	<camel:doCatch>
            		<exception>javax.ws.rs.ServiceUnavailableException</exception>
            		<bean ref="exceptionUtil" method="handleException"/>
            	</camel:doCatch>
	        </doTry>
        </route>

route1 and route3 throws and catch the exception and expected. 
But it doesnt happen the same with route2. The exception is not catch at all
and is very similar as route3.

for more information it would be better to say that invokerMainRoute throws
a javax.ws.rs.ServiceUnavailableException.

Thanks ! 



--
View this message in context: http://camel.465427.n5.nabble.com/Extrange-behaviour-of-exceptions-tp5786363.html
Sent from the Camel - Users mailing list archive at Nabble.com.