Issue - R39 - Make <completionCondition> element extensible

[ws-bpel issues list editor<peter@furniss.co.uk>]

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

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 - R39 - Make <completionCondition> element extensible

Status: received
Date added: 10 Nov 2006
Date submitted: 9 Nov 2006
Submitter: Trickovic, Ivana
Description: Completion condition of the <forEach> element can be only
an (unsigned) integer expression. Different implementations of WS-BPEL
may allow using arbitrary boolean conditions operating upon messages and
process variables, for example. However, the syntax of the
<completionCondition> element does not allow to include these vendor
specific extensions. 
Submitter's proposal: Make element <branches> optional and element
<completionCondition> extensible. The following changes to the syntax
should be made:
<completionCondition>?
    <branches expressionLanguage="anyURI"?
        successfulBranchesOnly="yes|no"?>?
        unsigned-integer-expression
    </branches>
    condition-element-of-other-namespace
</completionCondition>
instead of 
<completionCondition>?
    <branches expressionLanguage="anyURI"?
        successfulBranchesOnly="yes|no"?>
        unsigned-integer-expression
    </branches>
</completionCondition>
No change is required in the XML Schema since it already defines the
<completionCondition> element as extensible and the <branches> element
is optional (minOccurs="0").
Changes: 10 Nov 2006 - new issue

---

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - R39 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - R39 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document