Issue - 288 - Clarification of DPE and Sequence

[ws-bpel issues list editor <peter.furniss@erebor.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 - 288 - Clarification of DPE and Sequence

Status: received
Date added: 17 May 2006
Date submitted: 17 May 2006
Submitter: Danny van der Rijn
Description: If an activity in a sequence is skipped due to a joinCondition, does the next activity get executed?

Consider the following:

<sequence suppressJoinFailure="yes">


    <empty>
       <targets>
          <joinCondition>false</joinCondition>
          <target ... />
       </targets>
    </empty>


    <invoke .../>
<sequence>

The <empty> activity will never be run.  Will the invoke activity get skipped as well?

I don't think so, but the spec could be interpreted either way.
Changes: 17 May 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 - 288 - [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 - 288 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).