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: Re: [wsbpel] Issue - 246 - Instances of undefined behaviour


Resending, now that there's an issue # (thanks, Peter!)



Danny van der Rijn wrote:


Mark Ford wrote:
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.


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.




ws-bpel issues list editor wrote:

This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if a motion to open the issue is proposed and that motion is approved by the TC. A motion could also be proposed to close it without further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent version of the document entitled in the "Issues" folder of the WSBPEL TC document list - the next posting as a TC document will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.

Issue - 246 - Instances of undefined behaviour

Status: received
Date added: 9 Mar 2006
Categories: Specification editing
Date submitted: 8 march 2006
Submitter: Mark Ford
Description:

(issue list editor note: after the closure of issue 144 : Defining Undefined Behaviors , some possible instances of undefined behaviour have been found. This is raised as an issue for tracking purposes - some instances will be treated as action items)

#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.

Change to:

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:selectionFailure

Section 8.3 Expressions

(2nd to last paragraph)

This function extracts global property values from variables. The first argument names the source variable for the data and the second is the qualified name (QName) of the global property to select from that variable (see Variable Properties). If the referenced property is not defined or if there does not exist a propertyAlias to associate the property with the referenced variable then the semantics of the process is undefined.

This sentence in bold was introduced with the acceptance of Issue 145. The line should be changed to the following:

If the referenced property is not defined, if there does not exist a propertyAlias to associate the property with the referenced variable or if the given property definition selects a node set of a size other than one, then the standard fault bpws:selectionFailure MUST be thrown by a compliant implementation.

#3 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.

Strike the last two sentences since the bpws:missingRequest fault is detailed a few paragraphs later.
Changes: 9 Mar 2006 - new issue


To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 246 - [anything]" or is a reply to such a message. If you want to formally propose a resolution to an open issue, please start the subject line "Issue - 246 - Proposed resolution", without any Re: or similar.

To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



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