RE: [wsbpel] Issue - 111 - Proposal For Vote

["Trickovic, Ivana" <ivana.trickovic@sap.com>]

Shouldn't we specify that new activities must be defined as extensions
of complex type bpws:tActivity? 

-- Ivana

>-----Original Message-----
>From: Yaron Y. Goland [mailto:ygoland@bea.com] 
>Sent: Tuesday, May 31, 2005 11:26 PM
>To: wsbpeltc
>Subject: [wsbpel] Issue - 111 - Proposal For Vote
>
>111 - Extension Activities
>
>Proposal: Add an extensionActivityWrapper element to hold extension 
>activities
>
>Introduce Section 11.9
>
>New activities can be introduced for use in BPEL by placing 
>them inside 
>of the extensionActivityWrapper element. The contents of an 
>extensionActivityWrapper element MUST be a single element that 
>MUST make 
>available BPEL's standard-attributes and standard-elements. If the 
>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 
>unknown activity MUST be treated as if it were an empty 
>activity. In all 
>cases however any standard-attributes or standard-elements used on the 
>contained activity MUST be treated as defined by this specification.
>
><extensionActivityWrapper >
>    <???? standard-attributes>
>       standard-elements
>    </????>
></extensionActivityWrapper>
>
>Schema:
>
>Add to activity group:
><element name="extensionActivityWrapper" 
>type="bpws:textensionActivityWrapper"/>
>
>Add the following definition:
>     <complexType name="textensionActivityWrapper">
>         <sequence>
>             <any processContents="lax"/>
>         </sequence>
>     </complexType>
>
>
>---------------------------------------------------------------------
>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 
>
>