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.
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?
|Project Import||Sat Nov 27 00:14:50 EST 2010 [ 1290834890113 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||2.0.0 [ 11900 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Field||Original Value||New Value|
|Assignee||Claus Ibsen [ davsclaus ]||Hadrian Zbarcea [ hadrian ]|