Some customers have been asking for this. In order for proper coordination between the process creating the human task and the actual task, this is required. For example, if the process that created the human task terminated, then we need to terminate the human task which should be handled by the coordination protocol.
Regards Nandika On Mon, Jul 15, 2013 at 8:11 AM, Samisa Abeysinghe <[email protected]> wrote: > Also, what is the demand for this? Meaning, does this get used a lot out > there? > > > On Fri, Jul 12, 2013 at 1:58 PM, Srinath Perera <[email protected]> wrote: > >> Hi Hastha, >> >> Any updates? Do you need a meeting/review to discuss if you have an >> initial arch? >> >> --Srinath >> >> >> On Mon, Jul 8, 2013 at 7:43 AM, Hasitha Aravinda <[email protected]>wrote: >> >>> Hi all, >>> >>> Currently BPS don't support HumanTask Coordination Protocol [1][2] in >>> the humantask engine. Since this feature is required for some common >>> humantask use cases, and some users are also looking for this feature in >>> BPS, I did an initial research on the $Subject. >>> >>> In abstract, HumanTask Coordination Protocol is used to exchange >>> life-cycle command messages between BPEL process (or an Application) and an >>> invoked human task. That allows BPEL process to control the life cycle of >>> the human tasks and wise-versa. HumanTask Coordination Protocol uses >>> ws-Coordianation [3] to handle coordination between People Activity and >>> HumanTask. >>> >>> So I had a chat with Nandika and Srinath about this. So Idea is to >>> create ( Or reuse if possible ) a ws-coordination implementation module and >>> attached it to the both HumanTasnk engine and BPEL people activity >>> extension. Then achieve the HT coordination protocol message exchanges via >>> that module. >>> >>> We are also thinking to add this feature in switchable mode via BPS >>> configuration, to support backward compatibility. >>> >>> We will come up with proper architecture for this implementation and >>> will keep update the thread. Any suggestions/Ideas are welcome. >>> >>> Thanks, >>> Hasitha. >>> >>> >>> [1] - >>> http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html#_Ref231650654 >>> [2] - >>> http://docs.oasis-open.org/bpel4people/bpel4people-1.1-spec-cd-06.html#_Ref153150048 >>> [3] - >>> http://docs.oasis-open.org/ws-tx/wstx-wscoor-1.2-spec-os/wstx-wscoor-1.2-spec-os.html >>> >>> >>> -- >>> Hasitha Aravinda, >>> Software Engineer, >>> WSO2 Inc. >>> Email: [email protected] >>> Mobile: +94 71 8 210 200 >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> http://people.apache.org/~hemapani/ >> http://srinathsview.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
