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: Issue - 188 - Dead Path Elimination and Join Conditions

Title: Message
This issue has been added to the wsbpel issue list with a status of "received". The status will be changed to "open" if the TC accepts it as identifying a bug in the spec or decides it should be accepted specially. Otherwise it will be closed without further consideration (but will be marked as "Revisitable")

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 - 188 - Dead Path Elimination and Join Conditions

Status: received
Date added: 29 Jan 2005
Categories: State management
Date submitted: 27 January 2005
Submitter: Danny van der Rijn
Description: This is a question dealing with a pathological condition that the spec allows that I think we should disallow. Currently, it is legal to have a joinCondition which negates dead-path elimination. The simplest way to do this is to have an activity with one incoming link and whose joinCondition is not($incoming). A more detailed expression of this follows. Apologies if the syntax isn't quite right.

<flow suppressJoinFailure="yes">
       <link name="first2second"/>
       <link name="second2third"/>

          <source linkName="first2second">

          <source linkName="second2third">
          <target linkName="first2second"/>

          <target linkName="second2third"/>

A flow from first to second to third. The transition from "first" to "second" has some condition. If it is false, "second" will not evaluate. Yet according to my reading of the spec this merely sets the link status of "second2third" to false, which in turn causes "third" to execute.

This is in contradiction with my understanding of dead-path elimination.

Submitter's proposal: I would prefer to disallow joinConditions whose expression does not require a true input in order that the join condition evaluate to true. Comments?
Links:     Announcement, 29 Jan 2005
Changes: 29 Jan 2005 - new issue


Best Regards,


Tony Fletcher

Technical Advisor
Choreology Ltd.
68, Lombard Street, London EC3V 9L J   UK


+44 (0) 1473 729537


+44 (0) 7801 948219


+44 (0) 870 7390077




Business transaction management software for application coordination

Work: tony.fletcher@choreology.com

Home: amfletcher@iee.org


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