← Prev in month ← Prev in thread
Next in thread → Next in month →

Issue - R8 - Create separate isolation domain for isolated scope's compensation handler

From
ws-bpel issues list editor
Date
2006-09-18T23:51:05+00:00
ID
Thread
Issue - R8 - Create separate isolation domain for isolated scope's compensation handler
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 - R8 - Create separate isolation domain for isolated scope's compensation handler
Status: received

Date added: 18 Sep 2006

Date submitted: 18 September 2006

Submitter: Mark Ford

Description: Section 12.7 Isolated Scopes describes the compensation handler for an isolated scope as not sharing
the isolation domain for its associated scope. This is correct but it fails to define whether
the compensation handler has its own separate isolation domain. The result is that the compensation
handler for an isolated scope is not isolated. This leads to the inconsistency where compensation
handlers nested within an isolated scope will execute within an isolation domain only if called by
the isolated scope’s fault or termination handler and not if called by the isolated scope’s
compensation handler. This inconsistency was first raised as part III of 
Issue 10 but for some reason it was not part of the final proposed resolution. 

Changes: 18 Sep 2006 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - R8 - [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 - R8 - Proposed resolution", without any Re: or similar.

To add a new issue, 
see the issues procedures document
← Prev in month ← Prev in thread
Next in thread → Next in month →