[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue 132 - Proposal For Vote
I have included a HTML file with change markings reflecting the changes I understood us to agree to at today's F2F. Thanks, YaronTitle: Issue 132
132 - In-line Variable Initialization
Proposal: Allow in-line variable initialization in BPEL
Rationale: Many languages allow for variables to be initialized when they are declared so as to allow for an explicit relationship between the variable and its initial value. That way no one can accidentally insert code between the variable and its initialization thus causing various unforeseen problems.
Section 9.2. Variable
Change the variable syntax declaration to:
<variable name="ncname" messageType="qname"?
Insert the following paragraph after the paragraph that ends " However the children of the document element MUST exclusively consist of the complexType values assigned to the variable.":
A variable can optionally be initialized by using an in-line
from-spec. From-spec is defined in section 9.3. Conceptually the in-line
variable initializations are modeled as a virtual sequence activity that
contains a series of virtual assign activities, one for each variable being
initialized. The virtual assigns then each contain a single virtual copy whose
from-spec is as given in the variable initialization and the to-spec points to
the variable being created.
Change Schema for tVariable to:
<element ref="bpws:from" minOccurs="0"/>
<attribute name="name" type="NCName" use="required"/>
<attribute name="messageType" type="QName" use="optional"/>
<attribute name="type" type="QName" use="optional"/>
<attribute name="element" type="QName" use="optional"/>