Hi Camel community,
I am facing a problem using the Camel's deadLetterChannel.
I have several Routes that process messages and delegate to a Route-scoped
errorHandler when something bad happen (HTTP endpoint timeout for instance).
What I try to achieve is to implement a generic Route as deadLett
d users
> https://issues.apache.org/jira/browse/CAMEL-5959
>
>
> On Fri, Jan 11, 2013 at 7:44 PM, ncolomer <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=5725448&i=0>>
> wrote:
>
> > Hi Camel community,
> >
> > I am facing a problem using
olas
>
>
> 2013/1/12 Claus Ibsen-2 [via Camel] <
> ml-node+s465427n5725448...@n5.nabble.com>
>
> Hi
>>
>> I have logged a ticket to let the route id be accessible for end users
>> https://issues.apache.org/jira/browse/CAMEL-5959
>>
>>
>> O
Hi Camel community,
I'm back with another issue, about Route-scoped errorHandler this time.
I have several Routes that have their own errorHandler. Each of these
errorHandlers delegates Exceptions to a mutualized deadLetterChannel Route.
The deadLetterChannel Route finally persists on disk the o
Hi Claus,
Thanks for your answer. I imagine their is no way to retrieve the body as it
was received by the Route that failed? If so, is their any mechanism/pattern
that "spawns" a new Exchange (forcing initial message to current body)?
Regards,
Nicolas
--
View this message in context:
http:/
copy the body at the beginning of your route to a header/property.
>
> Sent from a mobile device
> Am 17.01.2013 23:04 schrieb "ncolomer" <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=5725785&i=0>>:
>
>
> > Hi Claus,
> >
>