[
https://issues.apache.org/jira/browse/CAMEL-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Lease updated CAMEL-17296:
--------------------------------
Description:
The option stopOnAggregateException has no effect. This was added in
CAMEL-10272, but since Camel 3.0, the MulticastProcessor method
isStopOnAggregateException is no longer called. If any exception is caught in
an aggregation strategy, it is set on the original Exchange object and the
processing is terminated, whether this option is set or not.
If the option is obsolete, it should be removed and the documentation and test
cases should be updated.
was:
The option stopOnAggregateException has no effect. This was added in
CAMEL-10272, but since Camel 3.0, the MulticastProcessor method
isStopOnAggregateException is no longer called. If any exception is caught in
an aggregation strategy, it is set on the original Exchange object the the
processing is terminated, whether this option is set or not.
If the option is obsolete, it should be removed and the documentation and test
cases should be updated.
> Multicast option stopOnAggregateException has no effect
> -------------------------------------------------------
>
> Key: CAMEL-17296
> URL: https://issues.apache.org/jira/browse/CAMEL-17296
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.13.0
> Reporter: Karen Lease
> Priority: Minor
>
> The option stopOnAggregateException has no effect. This was added in
> CAMEL-10272, but since Camel 3.0, the MulticastProcessor method
> isStopOnAggregateException is no longer called. If any exception is caught in
> an aggregation strategy, it is set on the original Exchange object and the
> processing is terminated, whether this option is set or not.
> If the option is obsolete, it should be removed and the documentation and
> test cases should be updated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
