New sub-issue 6.3: Partial Termination of a Scope

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue 6.3: Partial Termination of a Scope

Status: open
Date split: 31 May 2005
Categories: Expressions, State management
Submitter: Alex Yiu
Description: One question was highlighted when we were discussing whether an early-completion-enabled <flow> must use <scope>-based activities as branch activities. That question can be translated into whether we actually allow a "partial termination of a scope". The spec does not have a clear "yes" or "no" answer as of this moment. Regardless of whether we standardize early completion features or how early completion features look like, we must answer that "yes/no" question and add clarification accordingly.
Proposed resolution: Refer to attachment to Alex Yiu, 31 May 2005
Changes: 31 May 2005 - fields: Split, Title, Status, Submitter, Description, Proposed resolution

Best Regards,

Tony

	Tony Fletcher Technical Advisor Choreology Ltd. 68, Lombard Street, London EC3V 9L J UK
	Phone:	+44 (0) 1473 729537
	Mobile:	+44 (0) 7801 948219
	Fax:	+44 (0) 870 7390077
	Web:	www.choreology.com
Cohesions™
Business transaction management software for application coordination
Work: tony.fletcher@choreology.com
Home: amfletcher@iee.org

wsbpel message

Issue 6.3: Partial Termination of a Scope