Proposed Resolution for R33

[Simon D Moser <SMOSER@de.ibm.com>]

Page 26, assign Pseudo Syntax, fix to

<copy keepSrcElementName="yes|no"?
suppressFromSelectionFailure="yes|no"?>from-spec to-spec</copy>

********************
In Chapter 8.4, page 60, fix up the pseudo-syntax

<copy keepSrcElementName="yes|no"?>from-spec to-spec</copy>

to

<copy keepSrcElementName="yes|no"?
suppressFromSelectionFailure="yes|no"?>from-spec to-spec</copy>
*******************

On page 64 PRD, Section 8.4. Assignment, after the paragraph starting with
"The optional keepSrcElementName ...", insert a new Paragraph:

The optional suppressFromSelectionFailure attribute of the <copy> construct
is used to specify whether
a selectionFailure standard Fault is suppressed as specified in section
8.4.1 Selection Result of Copy Operations. The default value of the
suppressFromSelectionFailure is "no".

******************

In Section 8.4.1. Selection Result of Copy Operations, page 68 PRD, before
the paragraph starting with "When using the partnerLink ...", insert a new
paragraph:

If the optional suppressFromSelectionFailure attribute has the value of
"yes" and  the from-spec returns zero nodes then the <copy> would be a
"no-op" instead of throwing selectionFailure. Note that if selectionFailure
has been suppressed on the from spec, the value of the to spec is ignored.
The following table illustrates the behavior of the copy operation:

<< place Table here >>

********************

In section 8.4.1. Selection Result of Copy Operations, Page 68 PRD, change
from:

If the selection result of a from-spec or a to-spec belongs to Information
Items other than EII, AII
or TII, a bpel:selectionFailure fault MUST be thrown.

To

If the selection result of a from-spec or a to-spec belongs to Information
Items other than EII, AII
or TII, a bpel:selectionFailure fault MUST be thrown  ***(unless the
suppressFromSelectionFailure attribute on <copy> is set to "yes")***.

ÁND from

If the from-spec or to-spec do not select exactly one information item
during execution, then the standard fault bpel:selectionFailure MUST be
thrown.

to

If the from-spec or to-spec do not select exactly one information item
during execution, *** and  the suppressFromSelectionFailure attribute on
<copy> is set to "no" ***, then the standard fault bpel:selectionFailure
MUST be thrown.

**********************

In Appendix D. Examples of Replacement Logic, Part ( c ) EII-to-TII copy,
Example  2, (page 208 PRD) change from:

As no text node exists under"tns4:approvalNotice", a selectionFailure fault
will
be thrown, and no replacment logic executed.

To

As no text node exists under"tns4:approvalNotice", a selectionFailure fault
will be thrown, and no replacment logic executed *** because the default of
the suppressFromSelectionFailure attribute on <copy> is "no" ***.

**********************

In Appendix A, Table A.1. Standard Faults, change the description of
SelectionFailure from:

Thrown when a selection operation performed either in a
function such as bpel:getVariableProperty, or in an
assignment, encounters an error.

To

Should we do this ???
**********************

On page 70,

If the source is an EII with an xsi:nil="true", a selectionFailure fault
MUST be thrown. This check is performed during EII-to-AII or EII-to-TII
copy.

**********************















Cheers
/Simon
--------------------------------------------------
Simon Daniel Moser, M.Eng.
Business Process Solutions Development 1
IBM Boeblingen Laboratory
Schoenaicherstr. 220, 01/086
D - 71032 Boeblingen
Tel.: +49 - 7031 - 164304
IP Telephone Number (ITN): 39204304
email: smoser@de.ibm.com

Rule of thumb #3459835478: when you find yourself typing/copying the same
thing more than twice in a row, redesign or re-implement. No excuse
possible.