Issue - 150 - Message variables on invoke and reply

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

This issue has been added to the wsbpel issue list. 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 - 150 - Message variables on invoke and reply

Status: open
Categories: Syntax and validation
Date added: 20 Jul 2004
Submitter: Yaron Y. Goland
Date submitted: 20 July 2004
Description: The inputVariable is currently marked as optional on 
invoke activities but that doesn't make sense as we always require a 
message object in order to send a message.
Submitter's proposal: As things stand we should make the inputVariable 
mandatory. However, an alternative approach would be to have a friendly 
amendment to issue 12 : XML types and WS Interactions  to cover the case of messages with no parts. Both 
the WSDL 1.1 schema and WS-I seem to allow WSDL messages that have no 
parts. In that case a reasonable shortcut would be to make inputVariable 
optional on invoke as well as making both the faultName and variable 
attributes fully optional (as opposed to mutually exclusive) on reply in 
order to handle the 'no parts' case.
Changes: 20 Jul 2004 - 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 - 150 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 150 - 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).