[
https://issues.apache.org/activemq/browse/CAMEL-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43332#action_43332
]
Roman Kalukiewicz commented on CAMEL-159:
-----------------------------------------
Shouldn't exception propagation be handled by aggregationStrategy? I believe
that in case of splitter when we have one exception and few successful
responses it is not so obvious if it is an exception of not.
I believe that if aggregationStrategy aggregates the exception into result,
then it will be handled. Maybe we should simply verify if default aggregation
strategy used propagates those exceptions by choosing maybe the last one that
occurred.
> Splitter does not propagate exceptions
> --------------------------------------
>
> Key: CAMEL-159
> URL: https://issues.apache.org/activemq/browse/CAMEL-159
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Nicky Sandhu
> Fix For: 1.5.0
>
>
> Splitter in its process method iterates over the body of a message and
> processes each part synchronously. It does not propogate exceptions thrown by
> the processor when processing the exchange. This makes it problematic for
> tryBlock()....handleAll() kind of applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
