Actually this ought to be the current behavior. Use stop instead of suspend.
On Fri, Aug 9, 2013 at 4:54 PM, Claus Ibsen <[email protected]> wrote: > Hi > > Ah yeah well the idea would be that a suspend/resume will not restart > the counter. Where as a stop/start should do. Let me log a ticket > about this. > > > On Fri, Aug 9, 2013 at 10:30 AM, magner58 <[email protected]> wrote: >> Hi all, >> >> I use camel to implement some routine for user-triggered data consumption. >> When started/resumed it should poll data until there is no more and stop. >> >> My route looks like: >> from("timer:startPollingConsumer?delay=0&repeatCount=1").bean(myPollingConsumer); >> >> The problem is that single event without delay will be fired only when the >> route is started, but there will be none when it is resumed. Would it be a >> bug? >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Timer-with-delay-0-and-repeatCount-1-does-not-fire-after-resumed-tp5737036.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
