The camel aggregation example generates an error whenever the completion predicate is entered.

The camel aggregate example will generate an error every time that someone uses the completion predicate 'STOP'.

The problem is that prior to v2.8, the base convertor mechanism would return null if we are not able to convert the body to the desired type.
While from v2.8 onwards, this condition now generates an exception instead.

The example expects an Integer as a body but uses the string 'STOP' as a completion predicate.

There are two solutions that I was considering and would like your input.

Solution 1: Update the NumberAggregatorStrategy class in the aggregate example to return an Object instead of an Integer for the newExchange or surround the call with a try/catch/

Solution 2: Update the AggregateProcessor class so that the onAggregate method is called for the two exchanges iff the complete variable is not equal to 'predicate'.

Note that considering solution 2 would mean that the aggregate tests that depend on the completion predicate need to be updated to not assume that the predicate value is part of the aggregated exchange.