Or could we have an option like 'stopOnExceptionCount(3)' which means stop
on the third exception...
I would like to let the behavior as it is and maybe improve the
documentation if it's necessary. I didn't use the Splitter in conjunction
with the Aggregation strategy in the past. Do the Aggregator receive all
exchanges? Also the exchanges which throws the exception(s)?

Christian

Reply via email to