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: suppressJoinFailure default value


The XML schema in the appendix of the BPEL 1.1 spec 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, I think that
specifying a default value contradicts this statement in section 12.5.2:

<quote>
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.
</quote>

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.

If I am reading this wrong, perhaps someone can clarify.
Otherwise, I propose, in the schema's tActivity declaration, replacing this:
<attribute name="suppressJoinFailure" type="bpws:tBoolean" default="no"/>
with this:
<attribute name="suppressJoinFailure" type="bpws:tBoolean" use="optional"/>

Jim Clune
Parasoft Corporation          email: jim.clune@parasoft.com
101 E. Huntington Ave.      voice: (626) 256-3680
Monrovia, CA.  91016           fax  : (626) 305-9048



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