[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue 37 - Proposal to vote (updated)
Hi, all, (resend with a better subject line for Peter as suggested by Satish) (As requested by Diane ...) Here is a slightly updated version of Issue 37 proposal. Incorporated two data points mentioned by Peter in the previous email on this thread. Thanks! Regards, Alex YiuTitle: Issue 37 Proposal Draft
June 19, 2004 (Parts of Peter's email was incorporated into the proposal. Those changes are highlighted by underline and background color.) The "initiate" attribute becomes a tri-value switch
instead of a boolean switch. The legal values of the "initiate"
attribute are: "yes", "rendezvous", "no".
The default value of the attribute remains "no".
When a correlation set of "rendezvous" or "yes" initiation style is used with
a non-start inbound messaging activity, it must be accompanied with at least
one other correlation set which is already initiated and for which the
"initate" attribute is set to "no". Another way to state this constraint: for a non-start inbound activity, there must be at least one correlation set with initiate="no". There may be other correlation sets with "yes" or "rendezvous". Inbound messaging activites
are receive, onEvent and onMessage.
The purpose of this restriction, which applies only to non-start inbound
messaging activities, is to ensure that the associated message actually gets
delivered to the process instance in which the activity occurs. Start activities do not require this
restriction since the first such activity to receive a matching message actually
causes the creation of the process instance in which it occurs. Outbound messaging activities (reply and invoke) do not need this restriction since they have no
need for matching of message to the source process instance.
When a correlation set of "rendezvous" or "yes" initiation style is used with
a start activity, the "rendezvous" or "yes" initiated correlation set MAY be
the only correlation set used in the activity. For example, consider the following
non-start receive activity: <receive ... > The use of the correlation set "bar"
with a "rendezvous" initiation type is invalid since it is not accompanied by a correlation set with
initiation set to "no". Another illegal example that worths some highlighting: <receive ... createInstance="yes"> A correlation set used in a start activity must be un-initialized. Therefore, the initiate="no" pattern will definitely trigger an execution time fault.
Affected Sections:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]