Provide better support for Idempotent Receiver pattern [INT-2426]

[spring-operator]

Oleg Zhurakousky opened INT-2426 and commented

Although as you can see from the forum discussion it is already supported by the framework via many different components (Filter, Router, Aggragator) we probably need a a more formal support for something like \

---

Reference URL: http://forum.springsource.org/showthread.php?122716-Idempotent-Receiver

Issue Links:

• 7501 Document Scatter-Gather, Routing Slip and Idempotent Receiver Support

  ("is depended on by")

Referenced from: pull request https://github.com/spring-projects/spring-integration/pull/1286

7 votes, 8 watchers

[spring-operator]

Artem Bilan commented

Hey there! Let me express my view. It may look like:

<idempotent-filter id="fooIdempotent" input-channel="in" output-channel="out" disracd-channel="duplicate"
                   message-store="messageStore" expression="payload.id + '|' + payload.date"/>

where:

• id - is involved in 'messageGroupId' as it is in the <delayer>
• message-store - store messages in the group to identify duplicates in the future
• expression - the idempotent key

It should be covered by MessageGroup, because I may have several similar filters in the application. We can use expression evaluation result 'idempotent key' as message id for store, or iterate over entire group and compare results for each message.

I don't know... May be we can follow with Cammel expirience too (http://camel.apache.org/idempotent-consumer.html) and add other usefull options.

Of course, the case "Make balance $110" is not considered: it's fully up to the business logic of concrete application.

Cheers

[spring-operator]

Gary Russell commented

Merged