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: Action Items for undefined behavior


Title: Action Items for undefined behavior

I should have brought this up during the call but I was concentrating on taking minutes ;)

If there are no objections, I will open action items for the following spec text below that still contains undefined behavior.

#1 undefined changes to bpws:missingReply
5.5 The Lifecycle of a Business Process
(Paragraph 8)
A receive activity for an inbound request/response operation is said to be open if that activity has been performed and no corresponding reply activity has been performed. If the process instance reaches the end of its behavior, and one or more receive activities remain open, then the status of the instance becomes undefined. This condition indicates a modeling error that was not detected by static analysis.

Action: Change to the following:
A receive activity for an inbound request/response operation is said to be open if that activity has been performed and no corresponding reply activity has been performed. If the process instance reaches the end of its behavior, and one or more receive activities remain open, then the process faults with a bpws:missingReply. This condition indicates a modeling error that was not detected by static analysis.

#2 undefined changes to bpws:missingRequest
10.4 Providing Web Service Operations
(Paragraph beginning with "The correlation between a request and the corresponding reply…)
…For the purposes of this constraint, an onMessage clause in a pick is equivalent to a receive (see Pick). Moreover, a reply activity must always be preceded by a receive activity for the same partner link, portType and (request/response) operation, such that no reply has been sent for that receive activity. The semantics of a process in which this constraint is violated is undefined.

Action: Strike the last two sentences since the bpws:missingRequest fault is detailed a few paragraphs later. (Note: the text below has bpws:invalidReply but that is changing to bpws:missingRequest)

If a reply activity is being carried out during the execution of a business process instance and no synchronous request is outstanding for the specified partnerLink, portType, operation and correlation set(s), then the standard fault bpws:invalidReply MUST be thrown by a compliant implementation.



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