You're right - it should be:
And not
Many thanks again
Steven Hedges
IT - Credit Booking Derivs
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 29 September 2010 10:18
To: users@camel.apache.org
Subject: Re: Exception details
Jus
ontext.startRoute(DefaultCamelContext.java:607)
>>
>>
>> My theory is that the errroHandler (which is defined outside the
>> camelContext) cannot refer to a route (which is defined inside the
>> camelContext). Given that you said this was straightforward using the Java
>
eaker/deficient? Or have I hust made
> some obvois blatant error? (Latter is by far the most likely.)
>
>
> Thanks
>
> Steven Hedges
> IT - Credit Booking Derivs
>
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Se
atant error?
(Latter is by far the most likely.)
Thanks
Steven Hedges
IT - Credit Booking Derivs
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 28 September 2010 18:30
To: users@camel.apache.org
Subject: Re: Exception details
You need to set the errorHa
g help is much appreciated
>
>
> Steven Hedges
> IT - Credit Booking Derivs
>
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: 28 September 2010 16:35
> To: users@camel.apache.org
> Subject: Re: Exception details
>
> On T
---
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 28 September 2010 16:35
To: users@camel.apache.org
Subject: Re: Exception details
On Tue, Sep 28, 2010 at 5:27 PM, wrote:
> You realise I am going to have to get my 50 c of help now :-)
>
> Is it possible to use a route as an erro
e
any other route.
>
> Steven Hedges
> IT - Credit Booking Derivs
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: 28 September 2010 16:13
> To: users@camel.apache.org
> Subject: Re: Exception details
>
> On Tue, Sep 28, 20
.
(Config file releases are much simpler admin-wise than code releases).
Steven Hedges
IT - Credit Booking Derivs
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 28 September 2010 16:13
To: users@camel.apache.org
Subject: Re: Exception details
On Tue, Sep 28
;
> 10 The South Colonnade
> Canary Wharf,
> London E14 4PU,
> United Kingdom
>
> 02031344655
> x44655
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: 28 September 2010 14:33
> To: users@camel.apache.org
> Subject: Re: Except
e.org
Subject: Re: Exception details
On Tue, Sep 28, 2010 at 3:26 PM, wrote:
> I'll get the book...
>
> From the info on that page, is it correct to assume that it is impossible to
> get at the exception info from the Spring XML config? All I want to do is to
> log the a
>
>
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: 28 September 2010 14:09
> To: users@camel.apache.org
> Subject: Re: Exception details
>
> On Tue, Sep 28, 2010 at 2:49 PM, wrote:
>> Hi
>>
>> This is probably very strai
iginal Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: 28 September 2010 14:09
To: users@camel.apache.org
Subject: Re: Exception details
On Tue, Sep 28, 2010 at 2:49 PM, wrote:
> Hi
>
> This is probably very straightforward, but I've scoured the docs and can't
>
On Tue, Sep 28, 2010 at 2:49 PM, wrote:
> Hi
>
> This is probably very straightforward, but I've scoured the docs and can't
> find an answer.
>
> Is it possible to get details of the actual exception that occurred in an
> error handler? So far, I can see how to access the message that caused a
Hi
This is probably very straightforward, but I've scoured the docs and can't find
an answer.
Is it possible to get details of the actual exception that occurred in an error
handler? So far, I can see how to access the message that caused an error
(using the $body variable) but not the except
14 matches
Mail list logo
