Hello,
I played around with the Workflow module and the Ticket example some
more and found that the context is not persistent. It is also not
possible to create a custom context object, because the factory directly
calls Workflow::Context->new(). So I can't create my own persistent
context object (or can I ???).
In my planned application scenario for perl Workflow module I have long
running processes which require the cooperation of multiple teams. Example:
Shutdown Application on Server 1
Update Software on Server 1
Send schema update request to database team
Wait for approval of schema update
Start Applicatin on Server 1
Shutdown Application on Server 2
Update Software on Server 2
Send schema update request to database team
Wait for approval of schema update
Start Applicatin on Server 2
So it is possible for the workflow to be paused for a longer time and
the program is stopped. After the database team has approved the schema
update, the program is executed again. Now in the current
implementation, the context is lost.
How should I make the context persistent ? Any suggestions or "design
pattern" from users using Workflow for a longer time now ?
Regards,
Robert
|
