Sounds like a good use case for the Idempotent Consumer EIP http://camel.apache.org/idempotent-consumer.html <http://camel.apache.org/idempotent-consumer.html>
> On Feb 18, 2016, at 7:06 AM, gilboy <josephoto...@gmail.com> wrote: > > Hi > > My route calls a DB procedure which returns a large number of order objects. > > Before I send out the orders to a counterparty I want to examine the list of > orders and see if the same order ID appears as both a new order and a cancel > order, e.g. order 1001 returned as a new order and order 1001 returned as a > cancel order. If I find any instances of the above I want to remove the > order, i.e. not send 1001 out to counterparty. > > I looked at using the aggregator EIP but don't think its a great fit. Just > wondering if there is another more suitable EIP that fits this use case > > Thanks > Joe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Apache-Camel-EIP-to-process-batch-of-messages-identifying-those-which-can-be-filtered-tp5777844.html > Sent from the Camel - Users mailing list archive at Nabble.com.
