camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1234) Custom processing of Exchange before redelivery using DeadLetterChannel
Date Thu, 08 Jan 2009 10:12:59 GMT


Claus Ibsen commented on CAMEL-1234:

This needs to be a new feature.

* onException is a failure processor and is invoked instead of doing redelivery. So you can
alter routes in case a given exception is thrown
* intercept() kinda worked, but intercept doesn't sit between each and every node in the route

Best option is to build in into the DeadLetterChannel as its the orchestrator of doing redelivery.

> Custom processing of Exchange before redelivery using DeadLetterChannel
> -----------------------------------------------------------------------
>                 Key: CAMEL-1234
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
> We should provide a out-of-the-box solution to allow end users to do some custom processing
before DLC is attempting a redelivery on a given endpoint. The custom processing should only
be executed once per redelivery.
> Using the interceptor solution on the DLC wiki page will kick in for the remainder of
the routing for redelivered exchanges, forcing end users to keep track that they only modify
the exchange once per redelivery.
> The custom processing could be a detour route path

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message