Issue - 142 - Break & Continue

[ws-bpel issues list editor<peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list. 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 - 142 - Break & Continue

Status: open
Categories: Syntax and validation
Date added: 15 Jul 2004
Submitter: Yaron Y. Goland
Date submitted: 15 July 2004
Description: What if one is deep inside of a flow and want to exit 'successfully' as 
opposed to being forced to throw a fault?
What if one is deep inside of a while and want to immediately 
'successfully' continue to the next iteration as opposed to being forced 
to throw a fault?
Submitter's proposal: Currently if one needs to quickly 'jump' from one part of the code to 
another in a structured way the only option are faults. But faults, 
appropriately enough, imply error, which involve things like fault 
handlers, getting rid of compensation handlers, logging, etc. We really 
need a way to exit or continue 'successfully'. This is where break and 
continue would be very useful. We should probably also include named 
forms of break/continue.
Changes: 15 Jul 2004 - new issue

---

To comment on this issue, 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 - 142 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 142 - 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).