Hello John,

I have created a gist from your example that mimics what I am trying to do 
- https://gist.github.com/8bbfcd882c94fb363a58

In that example I get duplicate key error if I have update code below 
'super' in on_workitem and I get ide cant be null if i put it above super.

My goal here is to be able to update workitem fields while it is in the 
process of being consumed.
For example:
1) My participant gets called and on_workitem gets executed
2) on_workitem takes 1 hour to finish. in the end, workitem gets consumed 
(it is not a human participant - autoproceed)
3) During that one hour of work, I want be able to see updated info on 
workitem.

My initial though was to stick that info onto workitem fields and update it 
periodically while working on that workitem, but i got those errors. maybe 
my approach is wrong?

Thanks again,
Iuri


On Tuesday, December 11, 2012 9:09:25 PM UTC-6, John Mettraux wrote:
>
>
> On Tue, Dec 11, 2012 at 04:03:24PM -0600, Iuri Gagnidze wrote: 
> > 
> > Second problem is little bit confusing for me. I have a long running 
> > participant and I was trying to update some keys on workitem.fields so i 
> > can have up to date info when i query it or look at it through 
> ruote-kit. 
> > Basically inside my storage participant i execute this code: 
> > 
> > workitem.fields['count'] = count 
> > RuoteKit.engine.storage_participant.update(workitem) 
> > 
> > (...) 
>
> Hello Iuri, 
>
> I tried this 
>
>   https://gist.github.com/4264521 
>
> and it works fine for me. 
>
> Maybe this is what you want: 
>
>   https://gist.github.com/4264538 
>
> ? 
>
>
> 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

Reply via email to