On 2010-12-13 15.58, Paul Merlin wrote:
The Scheduler interface is only about scheduling using cron expressions for
now, ie. mostly repeating tasks, but it will be easy to add method like:
Schedule scheduleOnce( Task task, Long initialDelay );
Schedule scheduleOnce( Task task, Date date );
Where the implementation will generate the related cron expression.
I took this way as having several ways of scheduling (cron + delay + date)
would have cluttered the code. IMO having only one way to express scheduling
is simpler.
Cool, I'll update and check it out!
Since the previous discussion, I started an optionnal TimelineService to
expose past Task runs with their "result" (success/failed+details) and future
scheduled Task runs. This service could be used to expose scheduler state to
JMX for example. It's not functionnal yet but success/failure are already
recorded if the TimelineRecorderService is available.
Oooh.. when you say "timeline" I immediately associated it with the
Timeline AJAX widget. Would it be possible to make a REST resource that
exposes the Timeline JSON syntax? That would be veeeery cool!
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
