Issue - 203 - How to define a propertyAlias for a messageType

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

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

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 - 203 - How to define a propertyAlias for a messageType

Status: received
Date added: 15 Apr 2005
Categories: Data handling
Date submitted: 15 April 2005
Submitter: Yuzo Fujishima
Description: Now that we have passed the proposal for Issue 103 with $var.part amendment, currently there is no way to define a property alias for a message type because message part cannot be specified in a query string.

Below are some ideas:

A. Introduce a special variable "source" (or other proper name). Bind $source to the data from which the property value is derived.

Eg.

<propertyAlias propertyName="a:prop"
               messageType="b:msgTyp">
  <query>
    $source.part1/some/element/here
  </query>
</propertyAlias>
B. Consider a variable name in a query as a part name.

Eg.

<propertyAlias propertyName="a:prop"
               messageType="b:msgTyp">
  <query>
    $part1/some/element/here
  </query>
</propertyAlias>
C. Add messagePart attribute to propertyAlias element.

Eg.

<propertyAlias propertyName="a:prop"
               messageType="b:msgTyp"
               messagePart="part1">
  <query>
    /some/element/here
  </query>
</propertyAlias>
(Must a query start with "/"?)
Discussion:

With A, you can write something like concat($source.part1/some/element, $source.part2/another). Also, it is possible to apply the same mechanism to non-message-type sources.

B is similar to A and perhaps simpler. But B is not applicable to non-message-type sources. It is also somewhat inconsistent with representations used for assign, while, switch, and so on.

With C, query can be applied only to one part.
Submitter's proposal: Adopt A above.
Champions: Yuzo Fujishima <fujishima@bc.jp.nec.com>
Changes: 15 Apr 2005 - 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 - 203 - [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 - 203 - 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).

Choreology Anti virus scan completed