[
https://issues.apache.org/jira/browse/CAMEL-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055751#comment-17055751
]
Guillaume Nodet commented on CAMEL-14684:
-----------------------------------------
The {{Exchange.ERRORHANDLER_HANDLED}} property has been deprecated.
You should now use something like:
{code:java}
Boolean handled =
newExchange.adapt(ExtendedExchange.class).getErrorHandlerHandled();
oldExchange.adapt(ExtendedExchange.class).setErrorHandlerHandled(handled);
{code}
instead of
{code}
if (newExchange.properties.CamelErrorHandlerHandled) {
oldExchange.properties.CamelErrorHandlerHandled =
newExchange.properties.CamelErrorHandlerHandled
}
{code}
> Camel 3.1.0: error handling changed, route no longer stops
> ----------------------------------------------------------
>
> Key: CAMEL-14684
> URL: https://issues.apache.org/jira/browse/CAMEL-14684
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Remco Schoen
> Priority: Critical
> Attachments: BodyOnlyAggregationStrategy.groovy,
> BodyOnlyAggregationStrategyTest.groovy
>
>
> Hi,
> I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use a
> DeadLetterChannel and when the error has been handled, I expect the original
> route to stop and not to continue.
> When we use enrich we pass the exchange property CamelErrorHandlerHandled
> back to ensure the calling route stops, but that has changed. Is this correct
> and should we change our aggregation strategy?
> I added the strategy and it’s test.
> Kind regards,
> Remco Schoen
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
