wsbpel message

Subject: Issue - 131 - revisiting section 9.3.1 "Type Compatibility in Assignment"

From: ws-bpel issues list editor<peter.furniss@choreology.com>
To: wsbpel@lists.oasis-open.org
Date: Tue, 13 Jul 2004 03:54:28 +0100

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 - 131 - revisiting section 9.3.1 "Type Compatibility in Assignment"

Status: open
Categories: Data handling, Expressions
Date added: 13 Jul 2004
Submitter: Alex Yiu
Date submitted: 12 July 2004
Description:

Some of the constraints imposed by Section 9.3.1 "Type Compatibility in Assignment" in the current version of the specification (as of July 12, 2004) are not so reasonable.

For example, it said:

The from-spec is a variable of a WSDL message type and the to-spec is not, or vice versa. This is not legal because parts of variables, selections of variable parts, or endpoint references cannot be assigned to/from variables of WSDL message types directly.

If my reading is right, it outlaws a simple copy of a element or a text-node from a part of a WSDL message to a element-based or a simple-type-based variable and vice versa. This usage pattern is clearly needed.

Other considerations suggested by other TC members includes: simple type conversion: e.g. a string type => a boolean type conversion.

We need to re-visit that section of the specification and come up with a more reasonable of type compatiblity constraints.
Changes: 13 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 - 131 - [anything]" or is a reply to such a message. If you want to formally propose a resolution, please start the subject line "Issue - 131 - 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).