Yaron,
Perhaps I misspoke. I thought in the
context of the discussion on Issue#52, you had commented that deadlocks are
already possible in BPEL 1.1, in response to my claim that internal messaging
would introduce them for the first time.
My apologies if I mistakenly interpreted
that to mean serializable scopes in BPEL 1.1 already allow deadlocks because of
the locking they imply.
Satish
From: Yaron Goland
[mailto:ygoland@bea.com]
Sent: Wednesday, September 24, 2003
3:44 PM
To: wsbpel@lists.oasis-open.org
Subject: RE: [wsbpel] Issue - 67 -
Clarify semantics of serializable scopes
I'm not sure what the issue is referring
to vis a vis any comments I made. I'm not aware of serializable scopes
introducing any new deadlock issues that aren't already in BPEL [1]. After
all Serializable scopes are really nothing more than instructions to
the thread scheduler. So in theory any behavior you could see as a result
of a serializable scope could be reproduced by a sufficiently eccentric thread
scheduler.
[1] The use of serializable scopes and
links could cause deadlocks. But the authors understood this and so explicitly
banned the use of links that cross serialized boundaries in section 12.5.
-----Original Message-----
From: ws-bpel issues list editor
[mailto:peter.furniss@choreology.com]
Sent: Wednesday, September 24, 2003
1:28 AM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Issue - 67 -
Clarify semantics of serializable scopes
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
- 67 - Clarify semantics of serializable scopes
Status: open
Categories: concurrency control
Date added: 24 Sep 2003
Submitter: Satish Thatte
Date submitted: 23 September 2003
Champion: Satish Thatte
Document: Language specification,
section 13.6
Description: There has been some
recent discussion regarding the concurrency control semantics of serializable
scopes. Yaron Goland had also raised a question regarding the possibility of
deadlock among serializable scopes. This section needs additional wording to
clarify these issues.
Links: Ron
Ten-Hove, 15 Sep 2003
Changes: 24 Sep 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 - 67 - [anything]"
or is a reply to such a message.
To add a
new issue, see the issues procedures document.
To
unsubscribe from this mailing list (and be removed from the roster of the OASIS
TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.