John, There are many ways to skin that cat.
I would keep the start options in the fei. When a process is launched, I would update a new fei field: nextStartTime (for instance). When the process starts, that field could be updated using the options to determine the next nextStartTime. I can do this on my side if it gets too hairy on your side. Pat. > From: John Mettraux <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > Date: Mon, 29 Oct 2007 13:38:56 +0900 > To: <[email protected]> > Subject: [openwferu-users] Re: Flow Status with scheduling > > > Hi, > > OK, half a hint of a solution. > > If you have a one shot schedule like > > fei = engine.launch(process, :at => that_moment) > fei = engine.launch(process, :in => this_amount_of_time) > > You can do > > sleep_expression = engine.process_status(fei).expressions[0] > puts sleep_expression.awakening_time > puts sleep_expression.scheduler_job_id > > > For cron based launch schedules like > > fei = engine.launch(process, :cron => "0 5 * * *") > > you can't use engine.process_status(fei) > > You could turn to > > engine.get_scheduler.instance_variable_get("@cron_jobs") > > > To "normalize" this a little bit I could make sure that all the > scheduled job (cron- and at-style) do get a "__launch_schedule" tag > when scheduled, so that this becomes possible : > > jobs = engine.get_scheduler.find_jobs "__launch_schedule" > > > Wdyt ? > > -- > John Mettraux -///- http://jmettraux.openwfe.org > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
