Issue - 2 - Sub-Functions

[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 2656, It is hoped to have a fixed url for the ever-changing list.

Issue - 2 - Sub-Functions

Category: Requirement
Origin: Initial requirements log, item 2  (document details)
Date submitted: 23 May 2003
Submitter: Original authors group
Description:
A mechanism is needed that provides the capability to package standard bits of BPEL functionality and call them as sub-processes from within another BPEL process. Data to be exchanged between the calling process and the sub-processes is via parameter passing. Two mechanisms are proposed: a <call> activity that invokes the sub-process and waits until the sub-process has completed and a <spawn> activity that creates an instance of the sub-process with its own lifecycle and continues without waiting for the new instance to complete.

---

To comment on this issue, please follow-up to this announcement on the wsbpel-reqts@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 - 2 - [anything]".

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