Hi All,

We've been working on WS-Human Task implementation for the past few weeks
and this is an update on the current progress and what we are planning to do
next.

As mentioned in [1], we have re-factored the human task component's
architecture. The main idea was to separate human task specification logic
and allow the task engine to be run independently. So we have removed Carbon
dependencies and introduced new interfaces for user management and task
deployment. The code was temporarily committed to [2]. This produces a .war
file which could be deployed on a Servlet container.

The new code reflects the latest Human Task specification published  by
OASIS[3]. There are some significant changes from the older draft[4] which
was used for the human task implementation in BPS 2.0.0. We have added
support for sub tasks, deadline processing for the tasks and around 40+ new
task API operations were implemented.

There are several other functionality to be implemented according to the
spec. But at this stage we decided to focus on usability issues as we
currently support a limited set of UI features. So we are planning to
integrate the current code base to Carbon and focus on the UI
implementations.

Here is a list of items that we are planning to work on:
 - Adding a new human task editor.
 - UI functionality for Task Operations.
 - A new gadget for human tasks which could be used by task stakeholders for
rendering essential task information.

After these items are in place we'd focus on the rest of the
to-be-implemented functionality. Your input is appreciated.

Regards,
SanjayaV.

1:  http://markmail.org/thread/bjnkzlzvl63nhxmx
2:  https://svn.wso2.org/repos/wso2/people/sanjayav/humantask/trunk/
3:  http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cd-10.html
4:
http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-bpel4people/WS-HumanTask_v1.pdf
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to