[jira] [Commented] (CAMEL-6802) Using stopOnException in splitter should not copy result back as we should preserve original exchange

["Raul Kripalani (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781751#comment-13781751 ] 

Raul Kripalani commented on CAMEL-6802:
---------------------------------------

Hey Claus,

For me, this is not a black or white situation. When an exception occurs with stopOnException, it understandable that the user may require the (partial) aggregation result as an output + the appropriate Exception set on the exchange.

That way, they get the best of both worlds: (1) knowing that an Exception happened (and triggering any error handlers as a consequence) and (2) the output of the aggregation so far.

Perhaps we could introduce an option 'exchangeOnException' taking the values 'original' and 'aggregated_partial'?

Regards,
Raúl.

> Using stopOnException in splitter should not copy result back as we should preserve original exchange
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6802
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6802
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, eip
>    Affects Versions: 2.11.2, 2.12.1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.3, 2.12.2, 2.13.0
>
>
> If you use stopOnException on splitter then when an exception occurs then changes to eg exchange.properties should not override the input exchange, as that would not be expected.



--
This message was sent by Atlassian JIRA
(v6.1#6144)