camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acosent...@apache.org
Subject [camel] 04/04: Added idempotentConsumer EIP base docs
Date Tue, 31 Oct 2017 11:49:29 GMT
This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit da0efcdb1413852c76526ffc665f12ef7f1da356
Author: Andrea Cosentino <ancosen@gmail.com>
AuthorDate: Tue Oct 31 12:48:53 2017 +0100

    Added idempotentConsumer EIP base docs
---
 .../src/main/docs/eips/idempotentConsumer-eip.adoc | 52 ++++++++++++++++++++++
 1 file changed, 52 insertions(+)

diff --git a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
new file mode 100644
index 0000000..d4eea3e
--- /dev/null
+++ b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
@@ -0,0 +1,52 @@
+== Idempotent Consumer EIP
+
+The
+http://www.enterpriseintegrationpatterns.com/IdempotentReceiver.html[Idempotent
+Consumer] from the link:enterprise-integration-patterns.html[EIP
+patterns] is used to filter out duplicate messages.
+
+The Idempotent Consumer essentially acts like a
+link:message-filter.html[Message Filter] to filter out duplicates.
+
+Camel will add the message id eagerly to the repository to detect
+duplication also for Exchanges currently in progress. 
+ On completion Camel will remove the message id from the repository if
+the Exchange failed, otherwise it stays there.
+
+Camel provides the following Idempotent Consumer implementations:
+
+* MemoryIdempotentRepository
+* link:file2.html[FileIdempotentRepository]
+* link:hazelcast-component.html[HazelcastIdempotentRepository]
+(*Available as of Camel 2.8*)
+* link:sql-component.html[JdbcMessageIdRepository] (*Available as of
+Camel 2.7*)
+* link:jpa.html[JpaMessageIdRepository]
+* link:infinispan.html[InfinispanIdempotentRepository] (*Available as of
+Camel 2.13.0)*
+* link:jcache.html[JCacheIdempotentRepository]* (*Available as of Camel
+2.17.0)**
+* link:spring.html[SpringCacheIdempotentRepository] *(*Available as of
+Camel 2.17.1)**** 
+**
+* link:ehcache.html[EhcacheIdempotentRepository]** *(*Available as of
+Camel 2.18.0)****
+* link:kafka.html[KafkaIdempotentRepository] (*Available as of Camel
+2.19.0)*
+
+=== Options
+
+// eip options: START
+The Idempotent Consumer EIP supports 5 options which are listed below:
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *messageIdRepositoryRef* | *Required* Sets the reference name of the message id repository
|  | String
+| *eager* | Sets whether to eagerly add the key to the idempotent repository or wait until
the exchange is complete. Eager is default enabled. | true | Boolean
+| *completionEager* | Sets whether to complete the idempotent consumer eager or when the
exchange is done. If this option is true to complete eager then the idempotent consumer will
trigger its completion when the exchange reached the end of the block of the idempotent consumer
pattern. So if the exchange is continued routed after the block ends then whatever happens
there does not affect the state. If this option is false (default) to not complete eager then
the idempotent consumer will [...]
+| *skipDuplicate* | Sets whether to skip duplicates or not. The default behavior is to skip
duplicates. A duplicate message would have the Exchange property link org.apache.camel.ExchangeDUPLICATE_MESSAGE
set to a link BooleanTRUE value. A none duplicate message will not have this property set.
| true | Boolean
+| *removeOnFailure* | Sets whether to remove or keep the key on failure. The default behavior
is to remove the key on failure. | true | Boolean
+|===
+// eip options: END

-- 
To stop receiving notification emails like this one, please contact
"commits@camel.apache.org" <commits@camel.apache.org>.

Mime
View raw message