Hi John, Yes, it would be something like that.
In the meantime I came up with another possible solution. I would have two listeners. One listening for apply and other for reply events. That way I could have two kinds of notifications for "navi", when the workitem is delivered to the participant and when it comes back again to the engine. The reply listener would also remove field :navi as its final task which is something I need. I think I like this better... Wdyt? Lots of thanks for the help. Best regards, Gonzalo. On Wed, Dec 2, 2009 at 12:22 PM, John Mettraux <[email protected]> wrote: > On Wed, Dec 2, 2009 at 7:36 PM, Gonzalo <[email protected]> wrote: >> >> That way, a participant that executes the "consume" method, will call >> first a common "consume" method to process :navi param (the common >> behaviour) and then the "real" consume method gets executed. > > Hello, > > like in : > > ---8<--- > class YourParticipant > > def consume (workitem) > navi_consume(workitem) if workitem.params[:navi] > #... go on with regular consume > end > > def navi_consume (workitem) > # navi consume > end > end > --->8--- > > ? > > > -- > 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 -- 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
