On Sat, May 2, 2009 at 6:10 PM, harshal <[email protected]> wrote:
>
> Thanks for the explanation. It should suffice.
> But in long term, would like to consider any 'further sophisticated'
> mechanism than this ?
>
> I really don't know what 'further sophisticated' mean here, but a dumb
> this way to understand how existing (a neat and apparently very
> simple) scheme would not be sufficient, I thought I would ask it to
> you.

Hi Harshal,

maybe you mean something more "packaged". For example ruote-rest and
ruote-web2 "package" the replay mechanism in their web interface, the
mecha becomes :

  - browse processes
  - locate process with error
  - fix root issue
  - hit "replay"

> A couple of small doubts:
> * Where from the replay would begin during recovery process?

You just have to "replay" the error, the rest is taken care for you,
assuming you fixed the root issue of the error (else another,
identical, error will occur but you can replay it as well).

> * How are two instances of the same process are identified (I did not
> get this from journal example)?

In Ruote, process instances are identified by a "workflow instance
id", for example "20090414-gegetzubuni" or "20090403-jashiyakoro".

Expressions and Workitems belonging to a process instance are
identified by the workflow instance id (of the process instance) and
the "expression id" of their expression (their participant expression
for workitems). It something like "0.1.2" or "0.4.5".

Expressions and Workitems store this info in a field named "fei" (flow
expression id), classes of FlowExpressionId have accessors for wfid
"workflow instance id" and expid "expression id" and also wfname
(process definition name) and wfrevision (process definition revision)
and also wfurl (process definition url). So it's easy to know for a
workitem or an expression all the details of the owning process
instance.


I hope this will help, best regards,

-- 
John Mettraux   -   http://jmettraux.wordpress.com

--~--~---------~--~----~------------~-------~--~----~
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to