[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [bpel4people] New Issue: Relationship between composite task androuting pattern syntax
Target: WS-HumanTask Description: There is no section detailing relationship between composite task and routing pattern syntax Proposal: Introduce new section as below. This section will capture resolution in BP-92 and BP-108. 4.8 Composite Tasks and Routing Patterns Composite task syntax describes what different subtasks are executed in a complex task scenario. Routing patterns syntax describes who participates in such complex task scenario. A composite task, including subtasks of different task types, can be described only using the composite task syntax. A routing task containing a dynamic number of subtasks derived from the cardinality of the set of assigned people can be described only using the routing task syntax. Both syntax flavors MAY also be used in combination, which means that a composite task MAY include a complex people assignment and that any task defining a complex people assignment MAY become a composite task at runtime when adhoc subtasks are created. The runtime instantiation model and observable behavior for task instances MUST be identical when using composite task or routing pattern syntax. When composition is defined on a task, the composition MUST be applied for each of the potential owners defined in the task's people assignment.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]