Hello Klaus,
On Wed, May 09, 2012 at 01:40:59AM -0700, Klaus Schmidtmamn wrote:
>
> (...)
>
> My Participant-Impl:
>
> class SkilledParticipant < Ruote::StorageParticipant
> include Ruote::LocalParticipant
> def on_workitem
> puts "partitcipant-name: * #{workitem.participant_name}"
> level = workitem.participant_name.match(/^user_(\d+)/)
> .t_i
> puts "level=#{level}"
>
> puts "i am into local Participant now!"
> super
> reply_to_engine(workitem)
> end
> end
>
> (...)
>
> Sorry, but already I Do not understand why the "launch" action
> consumes the whole workflows, with all participants without waiting
> for a "proceed" action or waiting for the special participant, logged
> in.
It's because your #on_workitem, right after storing the workitem in the
storage thanks to the "super", immediately replies to the engine thanks to
"reply_to_engine(workitem)", that makes the workflow go on.
Never forget re-reading your code.
Thanks for the new thread of conversation,
--
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
