[
https://issues.apache.org/activemq/browse/CAMEL-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58497#action_58497
]
Claus Ibsen commented on CAMEL-1799:
------------------------------------
For example this notion is really not something that is intuitive. You should
of course just use {{deadLetterUri}} attribute to set the destination for the
DLQ
{code:xml}
+ <camel:errorHandler id="deadLetterErrorHandler" type="DeadLetterChannel"
handled="true">
+ <camel:redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="1000"
logHandled="true" />
+ <camel:deadLetter>
+ <bean class="org.apache.camel.component.direct.DirectEndpoint">
+ <constructor-arg>
+ <value>direct:start</value>
+ </constructor-arg>
+ </bean>
+ </camel:deadLetter>
{code}
> Spring DSL - Add error handler DSL support so we avoid having to use spring
> bean style
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-1799
> URL: https://issues.apache.org/activemq/browse/CAMEL-1799
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-spring
> Affects Versions: 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Fix For: Future
>
>
> We could use an DSL for error handling in Spring DSL
> Then we can use the <redeliveryPolicy/> tag as well. And have an enum to
> specify the type in case we want a dead letter channel instead or
> transactional instead
> {code:xml}
> <errorHandler id="myErrorHandler" type="DeadLetterChannel">
> <deadLetter uri="log:dead"/>
> <redeliveryPolicy maximumRedeliveries="5" logStackTrace="true"
> backOffMultiplier="2"/>
> </errorHandler>
> {code}
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
