On Thu, Dec 13, 2012 at 12:17:14PM -0800, Pedro Henriques dos Santos Teixeira wrote: > > can you help me figure it out what's ruote intented to do on this case: > > concurrence do > cursor :tag => 'C1' do > alpha > end > cursor :tag => 'C2' do > beta > jump :to => 'alpha', :ref => 'C1' > end > end
Hello Pedro, let's run that. https://gist.github.com/4279718 if you run it with NOISY=true (NOISY=true ruby pedro.rb), you'll see that alpha gets reached two times, the first time because concurrence "launches" all its branches, the second time because of the jump. > I wanted to have two workitems on 'alpha' (in parallle), but it seems the > jump replies to the concurrence, which then makes it terminates, is that > correct? I did not observe that. > I just started investigating, but would appreaciate opinion on how it > should behave. > > My motivation for this is when converting from a "2D workflow > representation" this would be a way of connecting / reusing activities. Maybe this new feature could help: https://github.com/jmettraux/ruote/blob/24995d71a054a02eb49e74f33383720055bfc79a/test/functional/ft_82_await_attribute.rb It's fresh on the master, very beta. It's the "await" expression (http://ruote.rubyforge.org/exp/await.html) reworked into an attribute. I'd like to write a blog post about it, but dayjob interferes. Help discussing/refining this new feature is 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
