wsbpel-reqts message

Subject: Issue - 31 - Unique identifier for establishing new correlation

From: ws-bpel issues list editor<peter.furniss@choreology.com>
To: wsbpel-reqts@lists.oasis-open.org
Date: Thu, 26 Jun 2003 18:38:29 +0100

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 - 31 - Unique identifier for establishing new correlation

Submitter: Assaf Arkin
Date submitted: 25 June 2003
Categories: enhancement
Document: Specification
Description:

A process needs to send a message and receive one or more respones asynchronously that are correlated and needs to use the correlation mechanism. The process is started with a request that contains values which are not known to be unique. There is a risk that using one of these values would result in the condition whereby a response is correlated to two or more processes. There needs to be a mechanism by which the process can decide on a unique value for the purpose of instantiating a correlation set.

A generic solution would introduce a new function that would generate a unique value, e.g. a UUID. A more specific solution would grant the process a single unique value that could be, e.g. the process instance identifier, accessible from a function or contained in a well defined variable/property.

Another solution would have the process use a property from the input message that is equivalent to the message identifier as specified by WS-Addressing. However, a complication may occur if the process is instantiated by two concurrent receive activities, either of which can decide on the correlation set value to use.

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 - 31 - [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.