Issue - 91 - Proposal to Vote

[Dieter Koenig1 <dieterkoenig@de.ibm.com>]

Proposed resolution for Issue 91: In abstract processes (only in abstract
processes!), allow omitting the nested activity of pick/onMessage,
eventHandlers/onEvent, and onAlarm. Change the BPEL XML schema in order to
make the activity subelement optional in these four places. Add explanatory
text to chapter 15.

Rationale: In abstract processes, one may want to hide the internals of
pick/onMessage, eventHandlers/onEvent, and onAlarm elements, without being
forced to insert an <empty/> activity.

New syntax - added '?' after "activity" (4 times):


   <pick createInstance="yes|no"? standard-attributes>
standard-elements        <onMessage partnerLink="ncname"
portType="qname"             operation="ncname"
variable="ncname"?>+            <correlations>?                <correlation
set="ncname" initiate="yes|no"?/>+           </correlations>
activity?       </onMessage>       <onAlarm (for="duration-expr" |
until="deadline-expr")>*            activity?       </onAlarm>
   </pick>

   <eventHandlers>?           <!-- there must be at least one onEvent or
onAlarm handler -->
           <onEvent partnerLink="ncname" portType="qname"
operation="ncname" messageType="qname"
variable="ncname">*               <correlations>?
<correlation set="ncname" initiate="yes|no"/>+
</correlations>               activity?           </onEvent>
<onAlarm for="duration-expr"? until="deadline-expr"?>*
activity?           </onAlarm>
   </eventHandlers>

Kind Regards
DK