Re: [wsbpel] Issue 190 - BPEL Internal Faults (New Proposed IssueAnnouncement)

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

I propose two amendments to the current proposal:

Amendment #1 - Change the default to 'no'. I don't believe it is 
appropriate to default to behavior that depends on proprietary 
extensions to be useful.

Amendment #2 - Require that the proposal be a bit more detailed. What 
language needs to be added to the spec to implement this proposal? Where 
does it need to be added? Specify how inheritance works for 
exitOnStandardFault. Etc. We keep finding that the devil is in the 
details and this proposal is detail light.

	Thanks,

		Yaron

Dieter Koenig1 wrote:
> I would like to modify my original Submitter's proposal for 190 by adding a
> suggestion for an explicit process/scope attribute (see the last paragraph
> below).
> Kind Regards
> DK
> 
> Submitter's proposal: Instead of allowing processes to catch these as
> standard faults, we propose that the process instance must *terminate*
> immediately when such a situation is encountered.
> 
> 
> The behavior of terminate is well-defined in BPEL -- as far as BPEL is
> concerned the instance execution ends when terminate 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".
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the 
> OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
>