I refer to the states defined in the HumanTask spec: http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cd-06.pdf Section 4.10 defines these states - "claimed" is not what the standard defines because different implementations had slightly different semantics, thus, we renamed the states and defined their operational semantics...
Best regards, Frank 2016-06-06 17:55 GMT+02:00 Manuranga Perera <[email protected]>: > There is no such status like "In progress". > > Isn't "claiming" a task is equivalent to making "in progress". > > In your example of call, I'll first claim and then start the call. > > On Mon, Jun 6, 2016 at 11:51 AM, Manuranga Perera <[email protected]> wrote: > >> I think as much as possible we have to achieve this with Event-driven >>> architecture rather than schedulers. >>> >> +1 >> >>> So we can use simple cache mechanism as below >> >> While this is possible, I don't see why we are trying to shave off a few >> milliseconds from the task creation and make the it more complex even >> sacrificing correctness. Isn't this some premature optimization ? >> >> -- >> With regards, >> *Manu*ranga Perera. >> >> phone : 071 7 70 20 50 >> mail : [email protected] >> > > > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
