You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Tracy Snell (JIRA)" <ji...@apache.org> on 2011/02/21 05:32:38 UTC
[jira] Commented: (CAMEL-3688) Add repeatCount option to timer
component
[ https://issues.apache.org/jira/browse/CAMEL-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997275#comment-12997275 ]
Tracy Snell commented on CAMEL-3688:
------------------------------------
timer:foo and timer:bar would create 2 endpoints so it should be fine to just store the repeatCount on the endpoint correct?
> Add repeatCount option to timer component
> -----------------------------------------
>
> Key: CAMEL-3688
> URL: https://issues.apache.org/jira/browse/CAMEL-3688
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.6.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.7.0
>
>
> Sometimes you may just want to trigger a route once on startup. And using a timer for that would be easy. But the timer will keep firing. So we need a {{repeatCount}} option.
> If we exceed the count then it should not emit any message.
> Ideally it should unschedule the task, and reset the count.
> Remember the current count is state full per timer task. So it needs to be stored on the task. As you can have multiple timer tasks running (eg with different names)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira