(resend with the Yaron's email address corrected)
Alex Yiu wrote:
Hi, all,
After talking to Paco and Satish in person, we prefer cutting the seond
half of the proposal off. Deferring that part of discussion to Issue
118 and Issue 96.
Thanks!
Regards,
Alex Yiu
Issue 37 Proposal Draft
Proposal
for Vote for Issue 37
June 23, 2004 -
10:25a.m PDT
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".
After a correlation set is initiated, the values of the
properties for a correlation set must be identical for all the messages
in all
the operations that carry the correlation set and occur within the
corresponding scope until the completion of the scope. This correlation
consistency constraint must be observed in all cases of
"initiate" values.
- When the "initiate" attribute is set
to "yes", the related activity MUST attempt to initiate the correlation
set.
- If the
correlation set is already initiated and the "initiate" attribute is set to "yes" ,
the standard fault bpws:correlationViolation MUST be thrown by a compliant
implementation.
- When the "initiate" attribute is set
to "rendezvous", the related activity MUST attempt to initiate the
correlation set, if the correlation set is NOT initiated yet.
- If the correlation set is already initiated and
the "initiate" attribute is set to "rendezvous",
the correlation consistency constraint MUST be observed. If the
constraint is violated, the
standard fault bpws:correlationViolation MUST be thrown by a compliant
implementation.
- When the "initiate" attribute is set
to "no", the related activity MUST NOT attempt to initiate the
correlation set.
- If an activity with the "initiate" attribute set
to "no" attempts to use a correlation set that has not been previously
initiated, the standard fault bpws:correlationViolation MUST be thrown by a compliant
implementation.
- If the correlation set is already initiated and
the "initiate" attribute is set to "no",
the correlation consistency constraint MUST to be observed. If the
constraint is violated, the
standard fault bpws:correlationViolation MUST be thrown by a compliant
implementation.
Affected Sections:
- 6.2. The Structure of a Business
Process
- 10.2. Defining
and Using Correlation Sets
- 14.4. Correlation
- Appendix D. XSD Schema
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
|