Issue - 283 - clarification on what happen to isolation domain sharing when a CH is called from FCT-Handler of an isolated scope

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 - 283 - clarification on what happen to isolation domain sharing when a CH is called from FCT-Handler of an isolated scope
Status: received

Date added: 5 May 2006

Date submitted: 05 May 2006

Submitter: Alex Yiu

Description: Currently, we don't have spec text to state what happen to isolation domain sharing when a CompensationHandler is called from an FCT-Handler (fault, compensation and termination handler) of an isolated scope. 

Submitter's Proposal: After the bullets headed by "The use of error handling features in an isolated scope is" , add: 

The compensation handler actually shares the isolation domain of the invoking FCT-handler of the immediately enclosing scope. 

Changes: 5 May 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 - 283 - [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 - 283 - 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).