CAMEL-8761: Idempotent Consumer EIP - Allow to commit when EIP scope ends

Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/134507a3
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/134507a3
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/134507a3

Branch: refs/heads/master
Commit: 134507a38da23eeeef54db76bb74bb1e8cec1d8b
Parents: 3c718ee
Author: Claus Ibsen <davscl...@apache.org>
Authored: Thu May 14 13:28:37 2015 +0200
Committer: Claus Ibsen <davscl...@apache.org>
Committed: Thu May 14 13:28:55 2015 +0200

----------------------------------------------------------------------
 .../camel/model/IdempotentConsumerDefinition.java       | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/134507a3/camel-core/src/main/java/org/apache/camel/model/IdempotentConsumerDefinition.java
----------------------------------------------------------------------
diff --git 
a/camel-core/src/main/java/org/apache/camel/model/IdempotentConsumerDefinition.java
 
b/camel-core/src/main/java/org/apache/camel/model/IdempotentConsumerDefinition.java
index 244bc50..8652390 100644
--- 
a/camel-core/src/main/java/org/apache/camel/model/IdempotentConsumerDefinition.java
+++ 
b/camel-core/src/main/java/org/apache/camel/model/IdempotentConsumerDefinition.java
@@ -109,14 +109,14 @@ public class IdempotentConsumerDefinition extends 
ExpressionNode {
     }
 
     /**
-     * Sets the scope of this idempotent consumer when its boundaries ends.
+     * Sets the scope of this idempotent consumer where its boundaries ends.
      * <p/>
-     * The default mode is <tt>onCompletion</tt> which means the idempotent 
consumer will
+     * The default mode is <tt>OnCompletion</tt> which means the idempotent 
consumer will
      * only trigger its completion at the end of the routing of the exchange, 
when the exchange completes.
      * So if the exchange is continued routed after the block ends, then 
whatever happens there <b>also</b> affect the state.
      * For example if the exchange failed due to an exception, then the state 
of the idempotent consumer will be a rollback.
      * <p/>
-     * The other mode <tt>blockOnly</tt> means that the idempotent consumer 
will trigger its completion
+     * The other mode <tt>BlockOnly</tt> means that 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.
      *
@@ -129,9 +129,9 @@ public class IdempotentConsumerDefinition extends 
ExpressionNode {
     }
 
     /**
-     * Sets the scope of this idempotent consumer where its boundaries ends to 
<tt>blockOnly</tt>.
+     * Sets the scope of this idempotent consumer where its boundaries ends to 
<tt>BlockOnly</tt>.
      * <p/>
-     * The <tt>blockOnly</tt> mode means that the idempotent consumer will 
trigger its completion
+     * The <tt>BlockOnly</tt> mode means that 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.
      *
@@ -146,7 +146,7 @@ public class IdempotentConsumerDefinition extends 
ExpressionNode {
     /**
      * Sets the scope of this idempotent consumer where its boundaries ends to 
<tt>onCompletion</tt>.
      * <p/>
-     * The <tt>onCompletion</tt> mode means the idempotent consumer will
+     * The <tt>OnCompletion</tt> mode means the idempotent consumer will
      * only trigger its completion at the end of the routing of the exchange, 
when the exchange completes.
      * So if the exchange is continued routed after the block ends, then 
whatever happens there <b>also</b> affect the state.
      * For example if the exchange failed due to an exception, then the state 
of the idempotent consumer will be a rollback.

Reply via email to