Re: [wsbpel] Action Items for undefined behavior

[Danny van der Rijn <dannyv@tibco.com>]

Title: Action Items for undefined behavior

Mark Ford wrote:

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.

Given that this is now much better spelled out, I would prefer just removing this paragraph altogether:  It is now not possible for a process to reach the end of its behavior with an open IMA that hasn't caused a fault already.  We may need to move the first sentence defining an open receive, although we'd have to reword it as an open IMA now anyway.

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.