On Tue, Sep 18, 2012 at 03:10:02PM -0700, Doug Bryant wrote: > > (...) > > I triple checked and electronic_signature_disagreed was indeed defined as a > StorageParticipant. This issue was resolved by renaming the > electronic_signature_disagreed step to electronic_signature_disagree. > > Does this sound like a bug in Ruote or expected behavior for changing a > Participant implementation?
Hello Doug, it sounds like the old participant (NoOp) was still registered on top of the participant list. Participant list before: - electronic_signature_disagreed: Ruote::NoOpParticipant - toto: Ruote::StorageParticipant Participant list after registration of new electronic_signature_disagreed: - electronic_signature_disagreed: Ruote::NoOpParticipant - toto: Ruote::StorageParticipant - electronic_signature_disagreed: Ruote::StorageParticipant I don't know what version of ruote you use or how you registered the participant, but that's a very likely scenario. You can do pp @dashboard.participant_list to look at what's currently in the participant list. Ruote 2.3.0 has the concept of register block and auto-clearing, you can read more about it at: http://ruote.rubyforge.org/participants.html#r_block I hope it will help, 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
