Issue - 228 - Importing propertyAliases

[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 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 - 228 - Importing propertyAliases

Status: received
Date added: 8 Sep 2005
Categories: Related standards
Date submitted: 07 September 2005
Submitter: Danny van der Rijn
Description: Property aliases are not in keeping with WSDL conventions. They are top 
level elements in WSDL definitions, but they are not named and are never 
directly referenced like other top-level WSDL elements (message, 
portType, binding, service, property, partnerLink,...). A BPEL engine is 
required to discover them to resolve property references for messages. 
And these property references do not mention the property alias at all, 
but rather a property and a variable (which in turn is associated with a 
message type). So one must scan through all property aliases in known 
(imported) WSDL and maintain a cross references to these aliases.  The 
question of what Property Aliases are included is not always an easy one 
to answer. For instance:

• Must PropertyAliases always be declared in the same WSDL as their referenced Properties?
• May PropertyAliases be defined in a <process> extension?

Perhaps forward references from property or process should be required.
Changes: 8 Sep 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 - 228 - [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 - 228 - 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