Issue - 300 - Can <fromParts> and <toParts> be omitted if WSDL message definition does not contain any parts?

[ws-bpel issues list editor <peter.furniss@erebor.co.uk>]

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 - 300 - Can <fromParts> and <toParts> be omitted if WSDL message definition does not contain any parts?

Status: received
Date added: 12 Jun 2006
Date submitted: 12 June 2006
Submitter: Thomas Schulze
Document: WS-BPEL 2.0 Committee Draft, section 10.3.
Description: The third paragraph in 10.3 is about WSDL messages without parts. It clarifies that the attributes variable, inputVariable and outputVariable MAY be omitted but it does not say if <fromParts> and <toParts> can be omitted for that case.

Submitter's proposal:

In section 10.3 change the third paragraph from:

> "One-way invocation requires only the inputVariable (or its equivalent
> <toPart>’s) since a response is not expected as part of the operation (see section Error! Reference source not found.). Request-response invocation requires both an inputVariable (or its equivalent <toPart>’s) and an outputVariable (or its equivalent <fromPart>’s). If a WSDL message definition does not contain any parts, then the associated variable attribute, inputVariable or outputVariable, MAY be omitted. Zero or more correlationSets can be specified to correlate the business process instance with a stateful service at the partner’s side (see section Error! Reference source not found.)."

to:

> "One-way invocation requires only the inputVariable (or its equivalent
> <toPart>’s) since a response is not expected as part of the operation (see section Error! Reference source not found.). Request-response invocation requires both an inputVariable (or its equivalent <toPart>’s) and an outputVariable (or its equivalent <fromPart>’s). If a WSDL message definition does not contain any parts, then the associated attributes variable, inputVariable or outputVariable, or the associated <fromParts> or <toParts> elements, MAY be omitted. Zero or more correlationSets can be specified to correlate the business process instance with a stateful service at the partner’s side (see section Error! Reference source not found.)."

Changes: 12 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 - 300 - [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 - 300 - 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).