OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue - 81 - Proposal For Vote


As a consequence of Paco's observations on issue 81 I realized a few 
things about the spec:

1) It never clearly specified that the start activity MUST complete 
executing before other activities, including other start activities in a 
multiple start activity scenario, are allowed to begin executing. This 
is heavily hinted at in section 11.4 but not explicitly stated.

2) The spec, near as I can tell, is not clear as to exactly what values 
should be used on correlation set patterns for start activities.

I therefore amend my previous proposal for issue 81 so as to address 
these two issues.

	Thanks,

			Yaron


Section 6.5

Change: To be instantiated, each business process must contain at least
one such "start activity." This must be an initial activity in the sense
that there is no basic activity that logically precedes it in the
behavior of the process.

To: To be instantiated, each business process must contain at least one
such "start activity." That is, a receive/pick activity annotated with a
createInstance="yes" attribute. See section 11.4 for more details on
start activities.

Change: If exactly one start activity is expected to instantiate the 
process, the use of correlation sets is unconstrained.

To: If a process contains exactly one start activity then the use of 
correlation sets is unconstrained.

Section 11.4

Change: A receive activity annotated in this way MUST be an initial
activity in the process, that is, the only other basic activities may
potentially be performed prior to or simultaneously with such a receive
activity MUST be similarly annotated receive activities.

To: A receive/pick activity annotated in this way MUST be a "start
activity". A "start activity" is an initial activity that has a
createInstance="yes" attribute defined on it. An initial activity is a
receive/pick activity where no other activities but scope, flow,
sequence and empty activities occur before it in the process's execution
path. While all start activities must be initial activities not all
initial activities are required to be start activities. If an initial
activity is not a start activity then the initial activity will only
become active after the start activity has completed execution.

Change: It is permissible to have the createInstance attribute set
to"yes" for a set of concurrent initial activities.

To: It is permissible to have multiple start activities. When a process 
begins execution the start activity that triggered the process MUST 
complete execution before the other start activities, now turned into 
initial activities, and any other initial activities begin execution.

Change: All such receive activities MUST use the same correlation sets
(see Correlation).

To: If a process has multiple start activities then all the start
activities MUST use the same correlation sets and the pattern for all 
the correlation sets MUST be sent to "rendezvous" (see Correlation).


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]