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 70 - Proposal to vote - resubmit


To make sure Peter's issue listing script will pick up the new contents of the issue 70 proposal, I am resubmitting the proposal with the required subject line. This proposal combines inputs from Jim Clune and Alex Yiu

Recap of the issue
--------------------
The BPEL schema in the appendix D declares a default value of "no" for the suppressJoinFailure attribute in tActivity and tProcess complexType declarations. This makes sense for tProcess, as it establishes a default to be used until overridden. For tActivity, however, specifying a default value contradicts this statement in section 12.5.2: 

		"A value of "yes" for [suppressJoinFailure] has the effect of suppressing the bpws:joinFailure fault for the activity and all nested activities, except where the effect is overridden by using the suppressJoinFailure attribute with a value of "no" in a nested activity." 

		By having the schema specify a default value for suppressJoinFailure for each activity element, nested activities always reset the value of suppressJoinFailure instead of inheriting it.


The proposal 
---------------
Make the following changes to the spec:

(1) To remove / change the wrong description default value of suppressJoinFailure attribute of an activity from section 6.2:
	
	Existing Text: 
	-----------------------------
	

	where the default values are as follows: 

	*	name. No default value (that is, unnamed)

	*	joinCondition. The logical OR of the liveness status of all links that are targeted at this activity

	*	suppressJoinFailure. No

	-----------------------------
	
	New Text: 
	where the default values are as follows: 

	*	name. No default value (that is, unnamed)

	*	joinCondition. The logical OR of the liveness status of all links that are targeted at this activity	

	*	suppressJoinFailure. In case the suppressJoinFailure attribute is omitted for an activity, it is inherited from its closest enclosing activity. 
		

(2) To remove / change the wrong description from section 11.1 "Standard Attributes for Each Activity":
	Existing description: 
	"The default value of suppressJoinFailure is no."
	New description: 
	"In case the suppressJoinFailure attribute is omitted for an activity, it is inherited from its closest enclosing activity"
	

(3)in Appendix B for Standard Attribute, specify the following in the "Defaults" column for suppressJoinFailure: 

"no for process element.  This attribute is optional for activities other than process. When not present for such an activity, it inherits its value from its closest enclosing activity."

(4) To change the description of Section 12.5.2. "Dead-Path-Elimination (DPE)":
	Existing description:
	"The default value of the suppressJoinFailure attribute is "no". This is to avoid unexpected behavior in simple use cases where complex graphs are not involved and links without transition conditions are used for synchronization. 
	New description:
	"The default value of the suppressJoinFailure attribute of process element is "no". This is to avoid unexpected behavior in simple use cases where complex graphs are not involved and links without transition conditions are used for synchronization. 

(5) change the BPEL schema (in appendix D and its OASIS location) to replace the current tActivity declaration: 

<attribute name="suppressJoinFailure" type="bpws:tBoolean" default="no"/>
  
with this: 
<attribute name="suppressJoinFailure" type="bpws:tBoolean" use="optional">

In addition, give the editors action to double check the spec and make editorial changes as they see appropriate to reflect resolution for this issue.

Best Regards,
Kevin
 


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