Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
When you use Camel's DLC as error queue, then when a message is moved to the DLQ, you may want to do some custom adjustment to the message before that happens.
As an end user you have the onPrepare where you can do that.
But for various Camel components then they may want to be able to hook in and be able to do some work.
For example you may may want to configure camel-jms or activemq-camel to store the caused exception message and stacktrace as JMS headers so they are avalable on the JMS queue. Also for ActiveMQ we want to allow it to store the original destination property so AMQ broker knows which original JMS message the message was consumed from. This makes redelivery from the web console or JMX easier, as its a click on a button.