[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [bpel4people] NEW ISSUE: B4P spec doesn't support error potentialowner
TARGET: WS-HT, General DESCRIPTION: WS-HT should support assigning the task to an error assignee if there are any errors in determining the potential owners. Computation of the potential owners of a task as part of people assignment involves complex operations like evaluating people queries, XPath expressions, etc. and as such errors might occur and a potential owner could not be identified. This will cause tasks erroring half way in complex routing logic RELATED ISSUES: · Support for routing patterns and policies · Support for single routing pattern · Support for sequential routing pattern · Support for parallel routing pattern PROPOSAL: Define an error potential owner is used to assign the task to when there is an error in task assignment during the evaluation of the potential owners. Error conditions include invalid task owners and incorrect XPath expressions in the people assignment. The error assignee will be able to reassign the task when such event happens. Syntax <xsd:complexType name="tOnErrorPotentialOwner"> <xsd:complexContent> <xsd:extension base="tExtensibleElements"> <xsd:sequence> <xsd:element name="from" type="tFrom"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> Example In the example below, the task will be assigned to the logical people group errorHandlers if there are any errors during the task assignment. <htd:peopleAssignments> … <htd:onErrorPotentialOwner> <htd:from logicalPeopleGroup="errorHandlers"> <htd:argument name="region"> htd:getInput("part1")/region </htd:argument> </htd:from> </htd:onErrorPotentialOwner> </htd:peopleAssignments>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]