Issue - 32 - Link Semantics in Event Handlers

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

This issue has been added to the wsbpel issue list. It is in the current version of the list at wsbpel document 2783, It is hoped to have a fixed url for the ever-changing list.

Issue - 32 - Link Semantics in Event Handlers

Status: open
Date added: 3 Jul 2003
Origin: Yuzo Fujishima, 2 Jul 2003
Submitter: Yuzo Fujishima
Date submitted: 02 July 2003
Document: BPEL 1.1 Specification
Description: According to 13.5.4.2 Message Events, BPEL 1.1 allows one event handler activity to run concurrently.

However, it is not specified whether all concurrent "threads" share link status or each

thread maintains its own link status. Suppose activity B has synchronization dependency

on A. Can B in a thread be run after A is completed in other thread? Or only after A is

completed in the same thread?
Links: Yuzo Fujishima, 26 May 2003
Satish Thatte, 26 May 2003
Yuzo Fujishima, 2 Jul 2003
Edwin Khodabakchian, 2 Jul 2003
Yuzo Fujishima, 3 Jul 2003
Changes: 3 Jul 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 - 32 - [anything]".

To add a new issue, send email to the wsbpel TC main list, adding a proposed title for the issue to the subject line. See the issues procedures document for further information.