You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/12/13 13:46:01 UTC

[jira] Created: (CAMEL-3424) IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate

IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate
---------------------------------------------------------------------------

                 Key: CAMEL-3424
                 URL: https://issues.apache.org/jira/browse/CAMEL-3424
             Project: Camel
          Issue Type: New Feature
          Components: camel-core
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.6.0


Currently you would have to subclass IdempotentConsumer and add custom logic in {{onDuplicateMessage}}.

End users may want to let some duplicates pass-through. So maybe we should have {{onDuplicateMessage}} return a boolean so we can determine what to do.
If it returns {{false}} (default) the message will be dropped. If it returns {{true}} the message is allowed and is continued to route.

We should then allow to set a custom predicate which can determine the onDuplicateMessage logic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3424) IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3424:
-------------------------------

    Fix Version/s:     (was: 2.6.0)
                   Future

> IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-3424
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3424
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: Future
>
>
> Currently you would have to subclass IdempotentConsumer and add custom logic in {{onDuplicateMessage}}.
> End users may want to let some duplicates pass-through. So maybe we should have {{onDuplicateMessage}} return a boolean so we can determine what to do.
> If it returns {{false}} (default) the message will be dropped. If it returns {{true}} the message is allowed and is continued to route.
> We should then allow to set a custom predicate which can determine the onDuplicateMessage logic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CAMEL-3424) IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3424:
-------------------------------

    Fix Version/s:     (was: Future)
                   2.7.0

> IdempotentConsumer EIP - Make it easier for end users to dicate onDuplicate
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-3424
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3424
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.7.0
>
>
> Currently you would have to subclass IdempotentConsumer and add custom logic in {{onDuplicateMessage}}.
> End users may want to let some duplicates pass-through. So maybe we should have {{onDuplicateMessage}} return a boolean so we can determine what to do.
> If it returns {{false}} (default) the message will be dropped. If it returns {{true}} the message is allowed and is continued to route.
> We should then allow to set a custom predicate which can determine the onDuplicateMessage logic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.