Issue - R38 - Wrong examples in 8.4

[ws-bpel issues list editor<peter@furniss.co.uk>]

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 - R38 - Wrong examples in 8.4

Status: received
Date added: 9 Nov 2006
Date submitted: 08 November 2006
Submitter: Thomas Schulze
Description: The following two examples copied from section 8.4 are
wrong. They show an <expression> element, but within <from> this element
is not allowed.

Example 1 on page 66 (word doc v01.182) - erroneous <expression> tag i shown in bold :

<variables>
   <variable name="A" element="foo:AElement" />
   <variable name="B" element="bar:BElement" />
</variables>
...
<sequence>
   <invoke ... inputVariable="..." outputVariable="A" />
   <assign>
      <from>
         <expression>
            bpel:doXslTransform("urn:stylesheets:A2B.xsl", $A)
         </expression>
      </from>
      <to variable="B" />
   </assign>
   <invoke ... inputVariable="B" ... />
</sequence>

Example 2 on page 66/67 (word doc v1.182) - erroneous <expression> tag i shown in bold:

<variables>
   <variable name="PO" element="foo:POElement" />
   <variable name="OutVar" element="foo:ItemElement" /> </variables>


<!-- ... PO is initialized ... -->


<!-- Iteratively add more items to PO until complete --> <while>
   <condition>...</condition>
   <sequence>
      <!-- Fetch next chunk into OutVar -->
      <invoke ... inputVariable="..." outputVariable="OutVar" />
      <assign>
         <copy>
            <from>
               <expression>
                  bpel:doXslTransform( "urn:stylesheets:AddToPO.xsl",
                  $PO, "NewItem", $OutVar)
               </expression>
            </from>
            <to variable="PO" />
         </copy>
      </assign>
   </sequence>
</while>

Submitter's proposal: Remove the <expression> and </expression> tags, the given
XPath expressions need to go directly into the <from> elements.

Change Example 1 to:

<variables>
   <variable name="A" element="foo:AElement" />
   <variable name="B" element="bar:BElement" />
</variables>
...
<sequence>
   <invoke ... inputVariable="..." outputVariable="A" />
   <assign>
      <from>
         bpel:doXslTransform("urn:stylesheets:A2B.xsl", $A)
      </from>
      <to variable="B" />
   </assign>
   <invoke ... inputVariable="B" ... />
</sequence>

Change Example 2 to:

<variables>
   <variable name="PO" element="foo:POElement" />
   <variable name="OutVar" element="foo:ItemElement" /> </variables>


<!-- ... PO is initialized ... -->


<!-- Iteratively add more items to PO until complete --> <while>
   <condition>...</condition>
   <sequence>
      <!-- Fetch next chunk into OutVar -->
      <invoke ... inputVariable="..." outputVariable="OutVar" />
      <assign>
         <copy>
            <from>
               bpel:doXslTransform( "urn:stylesheets:AddToPO.xsl",
               $PO, "NewItem", $OutVar)
            </from>
            <to variable="PO" />
         </copy>
      </assign>
   </sequence>
</while>

Changes: 9 Nov 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 - R38 - [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 - R38 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document