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: [wsbpel] Issue 190 - BPEL Internal Faults (New Proposed Issue Announcement)

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
Kind Regards

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".

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