On 10/28/07, Pat Cappelaere <[EMAIL PROTECTED]> wrote:
>
> John,
>
> I really think that scheduled execution of workflows is a rather critical
> feature of a workflow engine.
> For whatever my vote is worth, I would vote to keep that feature in.
2 ways to do that without the launch(process, schedule) trick
1). It's easy to write a process that does the scheduling of other
processes and to track that process (like the process it is).
2). It's easy to use the scheduler to launch a process :
job_id = engine.get_scheduler.schedule_at(that_moment) do
engine.launch(process)
end
Way 1 simplifies lots of things (actually that's how it's implemented
behind the scenes).
Now, back to your new requirement, for your new requirement, the
current launch(process, schedule) returns a handle to the scheduling
process, I could "decorate" the scheduling process for easy retrieval
of the information you need, but it's not as straightforward as you
think, and thus, the added complexity makes me wondering if I
shouldn't extract that scheduling from the workflow engine and promote
1 and 2.
I will investigate the process_status methods of the engine and make
sure they deliver the information you need (by querying the scheduling
process).
Best regards,
--
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
-~----------~----~----~----~------~----~------~--~---
