Re: Going back in a flow / restoring a flow
David Simón <[email protected]> Mon, 12 Sep 2005 13:41:36 +0200
| Newsgroups | gmane.comp.java.enhydra.shark |
|---|---|
| Message-ID | <[email protected]> |
Hello, I have double-checked the Shark API in order to find a solution to our restore flow issue and I have find some restore methods in the EventAuditManagerInterface. I have tried to understand their use but I am not sure about it. Does anybody knows if it is possible to use this methods to restore a flow context? I know I asked this before, but I would like not to make a work twice if Shark is already supporting it. Is there any way, by using these methods or by using the data stored in STATEEVENTAUDITS and DATAEVENTAUDITS, to restore the Process Context and the activities open in a moment in the past? Please, I would be grateful if somebody could answer to this and if somebody can provide an example would be great. I think Shark has all the information needed to perform this but I am not sure how. Anyway, if there are comments,criticals and so on, about our implementation proposal (see below) in case no other possibilities appear we would also be grateful. Thank you in advance. Best regards. David > Hello, > > > Regarding the subject "Going back in a flow" and since it seems Shark > does not provide a mechanism to perform this "back to the past" we are > planning to develop it. We think that a workflow engine should provide > administration mechanisms to go back in case anything is wrong. We do > not think that the approach would be to put back transitions in the > XPDL for all the activities, we believe that such behaviour should be > provided by the workflow engine in order to have maximum control of > the flows. > > Our proposal is as follows, and we would like to know your opinions as > Shark experts: > > We will have a database support to store process_contexts and open > activities. Everytime that an activity is going to be completed we > will store the process_context and a list of all the activities open > in that moment (in fact the type of activity, since the activity > instance id would be lost). In this way we have "checkpoints" of > different moments of a process instance. The administrator then can > choose one moment to go back and our mechanism would: > > -Abort all current open activities > -Restore the process_context > -Open again all the activities of the stored list that were open at > the moment of the checkpoint > > This is our first idea, what do you think about it? Do you think is > there any other way? > > Thank you very much. > > > Kind regards. > > David > > El lun, 29-08-2005 a las 14:25 -0400, Ben Anderson escribió: > > > David, > > afaik there is no capability to do this in shark. The solution to > > your problem would be to define an or split after activity B, which > > either goes back to activity A, or on to activity C. > > hth, > > Ben > > > > On 8/25/05, David Simón <[email protected]> wrote: > > > Hello, > > > > > > Another question in Shark 1.0 context. Is there any way to go back in a > > > flow to restablish the flow context in a time in the past (I mean, > > > activities open, values of variables in the context, assignments)? It is a > > > typical administration task that we need to provide but I would like to know > > > if there is any easy way through Shark API to do this. I have seen that > > > Shark has tables containing the history of the flow > > > (OLDEVENTAUDITDATA,STATEEVENTAUDIT and so on) so I guess it > > > is prepared to go back but I do not know how. > > > > > > Thank you. > > > > > > Best regards, > > > > > > David. > > > > > > -- > > > You receive this message as a subscriber of the [email protected] mailing > > > list. > > > To unsubscribe: mailto:[email protected] > > > For general help: mailto:[email protected]?subject=help > > > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > > > > > > > > > > > > > > plain text document adjunto (message-footer.txt) > > > > -- > > You receive this message as a subscriber of the [email protected] mailing list. > > To unsubscribe: mailto:[email protected] > > For general help: mailto:[email protected]?subject=help > > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws > > plain text document adjunto (message-footer.txt) > > -- > You receive this message as a subscriber of the [email protected] mailing list. > To unsubscribe: mailto:[email protected] > For general help: mailto:[email protected]?subject=help > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
message-footer.txt
(text/plain, 271 B)
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws