Return-Path: 
 <issues-return-3268-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D4CBD9D1F
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Wed, 25 Apr 2012 17:38:41 +0000 (UTC)
Received: (qmail 81457 invoked by uid 500); 25 Apr 2012 17:38:41 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 81429 invoked by uid 500); 25 Apr 2012 17:38:41 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 81419 invoked by uid 99); 25 Apr 2012 17:38:41 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 17:38:41 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Apr 2012 17:38:39 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 6CBE040E3D9
	for <issues@camel.apache.org>; Wed, 25 Apr 2012 17:38:18 +0000 (UTC)
Date: Wed, 25 Apr 2012 17:38:18 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <1718055367.1201.1335375498459.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1037360511.4894.1335190653949.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (CAMEL-5209) Describe default error handler
 configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CAMEL-5209?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian M=C3=BCller reassigned CAMEL-5209:
---------------------------------------

    Assignee: Christian M=C3=BCller
   =20
> Describe default error handler configuration
> --------------------------------------------
>
>                 Key: CAMEL-5209
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5209
>             Project: Camel
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.9.2
>            Reporter: Jakub Korab
>            Assignee: Christian M=C3=BCller
>            Priority: Trivial
>
> In the error handler documentation it is not obvious as to how to define =
a default error handler across all routes using the XML DSL. The informatio=
n is there, but hidden in the last section of a code block above the "Using=
 the transactional error handler" section.=20
> Could you please remove that part of the code block (starting with "<!-- =
You can also define the errorHandler inside the camelContext") and append t=
he following to the "Spring based configuration" section after the code blo=
ck:
> ---
> A default error handler may be configured by referencing it via the error=
HandlerRef attribute in the camelContext tag. This will be used across all =
routes that do not explicitly specify one of their own.
> -- code
> <camelContext errorHandlerRef=3D"globalErrorHandler" xmlns=3D"http://came=
l.apache.org/schema/spring">
>     <errorHandler id=3D"globalErrorHandler" type=3D"NoErrorHandler"/>
> </camelContext>
> -- code

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira