Issue 190 - Proposal For Vote

["Yaron Y. Goland" <ygoland@bea.com>]

I propose an amendment to the previous proposal that the default value 
for exitOnStandardFault be set to "no" so that our default behavior will 
also be our portable behavior. After all, exitOnStandardFault="yes" 
depends on proprietary functionality.

I also move that the proposal be amended so as to not apply to 
joinFailure as joinFailure is not necessarily a modeling error.

		Yaron


Dieter Koenig1 wrote:
> I move that the following proposal is adopted as resolution to issue 190.
> Note that the issue announcement text itself has been amended in the TC
> call on March 30, 2005.
> Kind Regards
> DK
> 
> ================================================
> 
> Submitter's proposal: Instead of allowing processes to catch these as
> standard faults, we propose that the process instance must *exit*
> immediately when such a situation is encountered.
> 
> Rationale: The behavior of "exit" is well-defined in BPEL -- as far as BPEL
> is concerned the instance execution ends when exit is encountered without
> any fault handling behavior. Any additional facilities for extended support
> for, e.g., repair and continue, is definitely out of scope.
> 
> This approach would also create a clear direction for dealing with any
> pathological situation within an inlined language (Issue 163) and therefore
> also for errors within transition conditions (Issue 169).
> 
> In order to support the behavior suggested here and also allow process
> modelers to continue using the current behavior, an explicit boolean
> attribute can be added to the <process> and <scope> elements:
>    <process/scope ... exitOnStandardFault="yes|no" ...>
> where the default is "yes".
> 
> ================================================
> Section 6.2. The Structure of a Business Process
> Add a new bullet under "The top-level attributes are as follows":
>  * exitOnStandardFault. If set to "yes" then a process must exit
> immediately
>    when a standard fault has been encountered (in the same way as if an
>    exit activity was reached). If set to "no" then a process can handle
>    the standard fault using a regular fault handler. The default is "yes".
> 
> ================================================
> New section 13.4.X Handling BPEL Standard Faults
> If the exitOnStandardFault attribute on a scope is set to "yes", then a
> process must exit immediately when a standard fault has been encountered
> in this scope (in the same way as if an exit activity was reached). If it
> is set to "no" then a scope can handle the standard fault using a regular
> fault handler. The default is "yes".
> 
> ================================================
> Appendix C. XML Schemas
> (add @exitOnStandardFault to complex types "tProcess" and "tScope")
> 
> 
> ---------------------------------------------------------------------
> 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
>