Issue - 234 - Link Crossing Termination Handler Boundary

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

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 - 234 - Link Crossing Termination Handler Boundary

Status: received
Date added: 15 Nov 2005
Categories: flow, link, termination
Date submitted: 14 November 2005
Submitter: Yuzo Fujishima
Document: 01SEP2005 Draft
Description: In 12.6. Flow, it is specified that
> * a link must not cross the boundary of a while or forEach
>   activity, an isolated scope, an event handler or a
>   compensation handler
and
> * a link that crosses a fault-handler boundary MUST be outbound.

Should there be any restriction for a link that crosses the boundary of a termination handler?
Submitter's proposal:

I think at least an incoming link into a termination handler must be prohibited because a termination handler should not / cannot wait for status determination of incoming links.

As for an outgoing link, I am not sure. Prohibiting it is perfectly fine with me. But for the same reason that an outgoing link from a fault handler is allowed, an outgoing link from a termination handler may be allowed.
Champions: Yuzo Fujishima <fujishima@bc.jp.nec.com>
Changes: 15 Nov 2005 - new issue

---

To comment on this issue (including whether it should be accepted), 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 - 234 - [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 - 234 - 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).