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 17:32:59 GMT


Claus Ibsen commented on CAMEL-1234:

Ah the above requires a bit of code as DLC needs to have a strategy to pick the correct onRedelivery
as well as it does for onException.

And it can get messy if during redeliver you have a complex route and it also throws an exception.
What should now happens?

So I am gonna make a simpler solution where you can declare on onRedelivery Processor on the
DLC that it invokes before redeliery. Then you can do a bit of custom alternation of the exchange
before its resend. This covers most use-cases.

If the above is requested by end users we can take another look later.

> 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