Camel
  1. Camel
  2. CAMEL-960

DeadLetterChannel - option to mark the exchange as failure handled and that its OK

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.5.0
    • Component/s: camel-core
    • Labels:
      None

      Description

      Currently the DeadLetterChannel sets the orignal caused exception on the exchange after it has been failure handled. We should support somekind of option to enable/disable this feature. We could support:

      • option on the endpoint to set this for all exchanges
      • support a special header key that end-users can insert per exchange to be more dynamic
      • maybe methods on Exchange to set this more easily
      • maybe some refinements in isFailureHandled() to cater for this

      And we should consider use a better keyname in the DLC where it stores the original exception.

      See nabble:
      http://www.nabble.com/JMS-%2B-Fault-td19778503s22882.html

      We might need to push this for Camel 2.0 but I think it is a feature that end-users would need sooner.

      Any thoughts, please write here?

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Hadrian Zbarcea
            Reporter:
            Claus Ibsen
          • Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development