wsbpel message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Issue R25 - Proposal to vote
- From: Diane Jordan <drj@us.ibm.com>
- To: wsbpel@lists.oasis-open.org
- Date: Tue, 14 Nov 2006 18:06:30 -0500
We discussed the following motion to
close R25 and deferred the vote. Please review the current motion
and potential amendment in preparation for the next discussion.
In secton 10.4, change
From: If during the execution of a business
process instance, two or more receive activities for the same partnerLink,
operation and correlationSet(s) are simultaneously enabled, then the standard
fault bpel:conflictingReceive MUST be thrown (note bpel:conflictingReceive
differs from bpel:conflictingRequest, see section 10.4.1. Message Exchanges).
To: If during the execution of a business process
instance, two or more receive activity instances for the same operation
and the same values of partnerLink and correlationSet(s)are simultaneously
enabled, then the standard fault bpel:conflictingReceive MUST be thrown
(note bpel:conflictingReceive differs from bpel:conflictingRequest, see
section 10.4.1. Message Exchanges).
Possible amendment discussed:
If during the execution of a business process instance,
two or more *IMA instances* for the same partnerLink, operation and correlationSet(s)
are simultaneously enabled, then the standard fault bpel:conflictingReceive
MUST be thrown (note bpel:conflictingReceive differs from bpel:conflictingRequest,
see section 10.4.1. Message Exchanges). *There are other cases where
two or more indistinguishable receive activity instances are enabled. In
these cases, a WS-BPEL processor MAY throw a bpel:conflictingReceive fault.*
Regards, Diane
IBM Emerging Internet Software Standards
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]