You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Jason Parr (Created) (JIRA)" <ji...@apache.org> on 2011/10/17 12:04:11 UTC
[jira] [Created] (CAMEL-4551) NotifyBuilder wereSentTo condition
fires too eagerly
NotifyBuilder wereSentTo condition fires too eagerly
----------------------------------------------------
Key: CAMEL-4551
URL: https://issues.apache.org/jira/browse/CAMEL-4551
Project: Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.9.0
Reporter: Jason Parr
Fix For: 2.9.0
Problem is:
NotifyBuilder notify = new NotifyBuilder(context)
.whenDone(2).wereSentTo("mock:bar");
The wereSentTo condition will fire after first message gets to endpoint "mock:bar", so either needs to take preceding whenDone into account, or wereSentTo needs to have a count condition added to it's method signature.
See nabble trail for full details:
http://camel.465427.n5.nabble.com/NotifyBuilder-condition-fails-to-match-on-an-out-activemq-endpoint-tp4689038p4867857.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4551) NotifyBuilder wereSentTo condition
fires too eagerly
Posted by "Claus Ibsen (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-4551:
----------------------------------
Assignee: Claus Ibsen
> NotifyBuilder wereSentTo condition fires too eagerly
> ----------------------------------------------------
>
> Key: CAMEL-4551
> URL: https://issues.apache.org/jira/browse/CAMEL-4551
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Jason Parr
> Assignee: Claus Ibsen
> Fix For: 2.9.0
>
>
> Problem is:
> NotifyBuilder notify = new NotifyBuilder(context)
> .whenDone(2).wereSentTo("mock:bar");
> The wereSentTo condition will fire after first message gets to endpoint "mock:bar", so either needs to take preceding whenDone into account, or wereSentTo needs to have a count condition added to it's method signature.
> See nabble trail for full details:
> http://camel.465427.n5.nabble.com/NotifyBuilder-condition-fails-to-match-on-an-out-activemq-endpoint-tp4689038p4867857.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4551) NotifyBuilder wereSentTo condition
fires too eagerly
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4551.
--------------------------------
Resolution: Fixed
Fixed this as well ordering does no longer matter. So you can configure wereSentTo anywhere.
Added better check the builder has at least one predicate configured.
> NotifyBuilder wereSentTo condition fires too eagerly
> ----------------------------------------------------
>
> Key: CAMEL-4551
> URL: https://issues.apache.org/jira/browse/CAMEL-4551
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Jason Parr
> Assignee: Claus Ibsen
> Fix For: 2.9.0
>
>
> Problem is:
> NotifyBuilder notify = new NotifyBuilder(context)
> .whenDone(2).wereSentTo("mock:bar");
> The wereSentTo condition will fire after first message gets to endpoint "mock:bar", so either needs to take preceding whenDone into account, or wereSentTo needs to have a count condition added to it's method signature.
> See nabble trail for full details:
> http://camel.465427.n5.nabble.com/NotifyBuilder-condition-fails-to-match-on-an-out-activemq-endpoint-tp4689038p4867857.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4551) NotifyBuilder wereSentTo condition
fires too eagerly
Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133598#comment-13133598 ]
Claus Ibsen commented on CAMEL-4551:
------------------------------------
You need to specify wereSentTo in the start, so it should be
NotifyBuilder notify = new NotifyBuilder(context)
wereSentTo("mock:bar").whenDone(2);
> NotifyBuilder wereSentTo condition fires too eagerly
> ----------------------------------------------------
>
> Key: CAMEL-4551
> URL: https://issues.apache.org/jira/browse/CAMEL-4551
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.9.0
> Reporter: Jason Parr
> Assignee: Claus Ibsen
> Fix For: 2.9.0
>
>
> Problem is:
> NotifyBuilder notify = new NotifyBuilder(context)
> .whenDone(2).wereSentTo("mock:bar");
> The wereSentTo condition will fire after first message gets to endpoint "mock:bar", so either needs to take preceding whenDone into account, or wereSentTo needs to have a count condition added to it's method signature.
> See nabble trail for full details:
> http://camel.465427.n5.nabble.com/NotifyBuilder-condition-fails-to-match-on-an-out-activemq-endpoint-tp4689038p4867857.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira