Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Onexception and try catch block in camel.
From: Quinn Stevenson <quinn@pronoia-solutions.com>
In-Reply-To: <1465241495711-5783511.post@n5.nabble.com>
Date: Mon, 13 Jun 2016 11:26:18 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCB6B2A2-2B13-4423-9759-61F0CB2C9C94@pronoia-solutions.com>
References: <1465241495711-5783511.post@n5.nabble.com>
To: users@camel.apache.org
archived-at: Mon, 13 Jun 2016 17:26:27 -0000

I=E2=80=99d suggest you read the =E2=80=9CError Handling=E2=80=9D =
chapter in =E2=80=9CCamel in Action=E2=80=9D - it covers onException =
very well.

For me, I use onException wherever possible - it allows me to use error =
handlers and exception policies which make my life much easier, and it =
separates the error handling logic from the routing logic.  I=E2=80=99m =
sure there are cases where you must resort to doTry, but I haven=E2=80=99t=
 had to.  If you do need doTry, keep in mind that Camel=E2=80=99s =
regular error handling no longer applies - you need to deal with =
everything yourself.

Hope that helps

> On Jun 6, 2016, at 1:31 PM, ravi21588 <ravi21588@gmail.com> wrote:
>=20
> Hi All,
> Onexception clause and try catch block both can be specified in with =
in a
> camel route.
> Can you please let me know the difference and advantage of using one =
upon
> other.
>=20
>=20
>=20
> --
> View this message in context: =
http://camel.465427.n5.nabble.com/Onexception-and-try-catch-block-in-camel=
-tp5783511.html
> Sent from the Camel - Users mailing list archive at Nabble.com.