Issue - 79 - Serializable scopes do not need to be leaf scopes

[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 document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting 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 - 79 - Serializable scopes do not need to be leaf scopes

Status: open
Date added: 22 Oct 2003
Submitter: Ron Ten-Hove
Date submitted: 22 October 2003
Document: BPEL 1.1 Specification
Description: The specification states that "Serializable scopes must not be nested. A scope marked
with variableAccessSerializable="yes" must be a leaf scope."

The latter requirement is too restrictive. Sub-scopes can be included in a serializable scope, and will be treated as logically part of the serializable scope. What should be banned are nested serializable scopes.
Links: Satish Thatte, 22 Oct 2003     Dieter Roller, 22 Oct 2003
Changes: 22 Oct 2003 - 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 - 79 - [anything]" or is a reply to such a message.

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