Issue - 111 - Proposal For Vote

[Francisco Curbera <curbera@us.ibm.com>]

111 - Extension Activities

Proposal: Add an extensionActivityWrapper element to support extension
activities

Introduce Section 11.9

New activities can be introduced for use in BPEL by using the
extensionActivityWrapper element. An extensionActivityWrapper element MAY
contain BPEL's activity standard-attributes and standard-elements;
additionally, it MUST contain a single extensibility element from a
namespace different form the BPEL namespace, which provides the information
required to execute the extensible activity.

If the extension element contained within the extensionActivityWrapper
element is not recognized by the BPEL processor and is not subject to a
mustUnderstand="true" requirement from an extension declaration then the
new activity MUST be treated as if it were an empty activity.

<extensionActivityWrapper standard-attributes>
       standard-elements
    <???? >
     ...
    </????>
</extensionActivityWrapper>

Schema:

Add to activity group:

<element name="extensionActivityWrapper"
type="bpws:textensionActivityWrapper"/>

Add the following definition:

<complexType name="textensionActivityWrapper">
      <complexContent>
          <sequence>
                <element name="targets" type="bpws:tTargets"
minOccurs="0"/>
                <element name="sources" type="bpws:tSources"
minOccurs="0"/>
                <any namespace="##other" processContents="lax"/>
            </sequence>
            <attribute name="name" type="NCName"/>
            <attribute name="suppressJoinFailure" type="bpws:tBoolean"
use="optional"/>
            <anyAttribute namespace="##other" processContents="lax"/>
      </complexContent>
 </complexType>