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 - 270 - Copying a message variable with uninitialized parts
Status: received
Date added: 26 Apr 2006
Date submitted: 25 April 2006
Submitter: Mark
Ford
Description: Does a copy operation which copies a source
message variable to a target message variable throw a
bpel:uninitializedVariable if one of the parts in the source message is
uninitialized?
<copy>
<from variable="messageA"/>
<to variable="messageB"/>
</copy>
Submitter's proposal: After reviewing Section 8 I think it
could go either way. If one were to treat the copy operation as
"reading" the part then Section 8.1 says that it should throw. If this
copy operation is not considered a "read" of the part, then Section
8.4.2 indicates that we would not throw.
Section 8.1 states:
An attempt during process execution to read a variable
or, in the case of a message type variable, a part of a variable before
it is initialized MUST result in the standard
bpel:uninitializedVariable fault.
Section 8.4.2 states:
When the from-spec and to-spec of a <copy>
operation both select WSDL message variables, the value of the
from-spec message variable MUST be copied, becoming the value of the
to-spec message variable.
If the intention is to allow the copying of the uninitialized parts
then this should be made explicit in Section 8.4.2. If this is not the
intention, then perhaps reiterating the uninitialized fault in Section
8.4.2 is sufficient to make this clear.
Changes: 26 Apr 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 - 270 -
[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 - 270 - 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).
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php