On Wed, Sep 16, 2009 at 1:00 AM, Charles.Magid <[email protected]> wrote: > > Could you help me understand what you mean by the participant > registration in line 25 of gist http://gist.github.com/186443?
Hi Charles, sorry for the late reply. This participant relies on the :merge => "isolate" config for the concurrent_iterator (see [1], [2] and [3]). It will gather the values found in the fields 0 to n (where n is the numbers of invitations sent out). If those 'subfields' contain "coming?" => "yes" then the field "invited" is added to the compilation (see updated gist at [4]). When no more index fields are found, the loop breaks and the compilation of coming invited person is placed in the workitem field named "coming". Then the block participant implicitely replies to the ruote engine and the process instance resumes. [1] http://ruote.rubyforge.org/exp/concurrence.html [2] http://github.com/jmettraux/ruote/blob/ruote2.0/test/functional/eft_6_concurrence.rb#L155-162 [3] http://github.com/jmettraux/ruote/blob/ruote2.0/test/functional/eft_18_concurrent_iterator.rb#L291-310 [4] http://gist.github.com/187855 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 -~----------~----~----~----~------~----~------~--~---
