OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - 297 - Does correlation require a propertyAlias with messageType attribute?


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 - 297 - Does correlation require a propertyAlias with messageType attribute?

Status: received
Date added: 10 Jun 2006
Date submitted: 09 June 2006
Submitter: Mark Ford
Description: I'd like a clarification as to the use of a propertyAlias for message correlation. My reading is that the spec requires a propertyAlias with a messageType in order to extract values for correlation. In cases where an activity like a <receive> uses an elementType variable for its data the spec explains that an anonymous temporary WSDL message variable is created for the data and its single part is used to populate the element variable on the <receive>. The same wording (anonymous temporary WSDL message variable) is used to explain <fromPart> and <toPart> behavior.

If the intent is to allow propertyAlias with elementType then we would need to define which propertyAlias would be used in the case that there was a messageType and an elementType since they could have different queries.

If the intent is to require a propertyAlias with messageType then some additional text to Section 9.2 could make this explicit.
Submitter's proposal:

In Section 9.2, change

--- from ---

Observe that in order to retrieve correlation values from a message, a processor needs to apply a particular <propertyAlias> to the message. In the case in which the application of the <propertyAlias> results in a response that contains anything other than exactly one information item and/or a collection of Character Information Items then a bpel:selectionFailure fault MUST be thrown.

--- to ---

Observe that in order to retrieve correlation values from a message, a processor MUST apply a <propertyAlias> with a messageType value that matches the QName of the message. In the case in which the application of the <propertyAlias> results in a response that contains anything other than exactly one information item and/or a collection of Character Information Items then a bpel:selectionFailure fault MUST be thrown.

Changes: 10 Jun 2006 - 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 - 297 - [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 - 297 - 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).



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]