On Fri, Jun 15, 2012 at 04:07:40AM -0700, Christophe Malaurie wrote:
>
> - we usually register a process with a :name tag. How can I get the list of
> defined processes (not running as with engine.processes) with their names
> and corresponding identifiers ? I would like to launch processes using
> their name as and identifier , so if I have the list name/id I can do that.

Hello Christophe,

sorry, there is no concept of "registered process/workflow [definitions]" in
ruote. I know that such concept exist in other workflow/BPM engines, but I
chose to stay simple, ruote being simply an interpreter.

I tend to implement such things by placing the definitions in a directory (or
hierarchy of directory) and, when prompted, listing the files and inferring
the definition name from the filename (or by quickly reading/parsing the
file).

I've seen people place the definitions in databases with
name/revision/definition columns or variants of that.

> - :on_error expression. What causes an error to be propagated to the engine
> from a participant ? Is it just using the Ruby "raise" so exception is
> propagated to the worker? I saw how to get the error message in an example
> but could not figure out if there was a particular way for participants to
> raise an error.

Yes, from a participant you simply do a Ruby "raise" (or "fail") and the
error is passed (and intercepted) by the engine.

If you have a remote participant (a pair local participant coupled to a
remote participant) you can raise on the local side or fetch the error and
use a "raise" msg locally (see

  
https://github.com/jmettraux/ruote/blob/65acf4c1436ba3f8a846a68a8a75e0cb586c70e7/test/functional/ft_73_raise_msg.rb

but this is quite recent on the ruote master).


Questions are welcome, best regards,

--
John Mettraux - http://lambda.io/jmettraux

-- 
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