Issue - 1 - Permeability of scopes

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

This issue has been added to the wsbpel issue list. It is in the current version of the list at wsbpel document 2656, It is hoped to have a fixed url for the ever-changing list.

Issue - 1 - Permeability of scopes

Category: Requirement
Origin: Initial requirements log, item 1  (document details)
Date submitted: 23 May 2003
Submitter: Original authors group
Description:
Currently scopes are "permeable" in the sense that the status of links that are used for activity synchronization is visible outside the scope before the scope completes.  This has problematic implications in case the scope faults.  Should we support non-permeable scopes, i.e., scopes that make the status of links that are used for activity synchronization invisible outside the scope until the scope completes (normally or abnormally). Should we support the notion of non-permeable scopes?  Only non-permeable scopes?  Both?

---

To comment on this issue, please follow-up to this announcement on the wsbpel-reqts@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 - 1 - [anything]".

To add a new issue, send email to the wsbpel requirements and issues coordination list, adding a proposed title for the issue to the subject line. See the issues procedures document for further information.