RE: [bpel4people] BP-36: Getting all task details in a single request

["Michael Rowley" <michael.rowley@activevos.com>]

 

In yesterday’s meeting we informally agreed that this should be handled by a new operation:

 

getTaskDetails

 

returns any or all details of a task, except the contents of the attachments.

 

Parameters:

- taskID:

The id of the task being queried.

- properties:

Optional list of properties of the task that should be provided. Properties are named by the local part of the QName of the element returned for task details.
If it is not specified, then all properties are returned.
If it is specified, then only the properties specified are returned.  In the case that multiple elements have the same local part (which can happen for extensions from two different namespaces) then all of the matching properties are returned.

- renderingPreferences:

Optional list of rendering types, in order of preference. 
If properties is not specified or includes “renderings” then…
     If renderingPreferences is not specified, the result includes all renderings. 
     If it is specified, then the task’s rendering whose type is earliest in the provided list of rendering types is returned.

 

I will be drawing up a more formal proposal.

 

Michael

 

 

---

From: Luc Clement [mailto:luc.clement@activevos.com]
Sent: Thursday, September 11, 2008 6:45 PM
To: 'Michael Rowley'; bpel4people@lists.oasis-open.org
Subject: [bpel4people] BP-36: Getting all task details in a single request

 

Assigned: http://www.osoa.org/jira/browse/BP-36

 

From: Michael Rowley [mailto:michael.rowley@activevos.com]
Sent: Thursday, September 11, 2008 17:23
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] NEW ISSUE: Getting all task details in a single request

 

 

TARGET: WS-HT

 

DESCRIPTION:

 

Currently, the WS-HT interface is fine grained.  If an application wants to present the user with all the information about a task on a single screen (other than the contents of the attachments, which are accessed separately), then it would be necessary to call all of the following operations in the current interface:

-          getAttachmentInfos

-          getComments

-          getRenderingTypes

-          getRendering

-          getTaskInfo

-          getTaskDescription

-          getInput

-          getOutput

-          getFault

-          getOutcome

 

PROPOSED RESOLUTION:

 

We should add an operation called: getTaskDetails which returns all of the information about a task other than the contents of its attachments.  This operation takes a task ID as input and returns a union of the contents returned by the operations listed above.  Some of the operations above require an additional parameter to get a specific item (getRendering, getTaskDescription, getInput and getOutput).  The getTaskDetails operation returns all valid return values of these operations for the given task ID (all renderings, task descriptions, inputs and outputs).