[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - 106 - ASSERT activity.
1) +1 2) -1 ----- Original Message ----- From: "Ricky Ho" <riho@cisco.com> To: <wsbpel@lists.oasis-open.org>; <wsbpel@lists.oasis-open.org> Sent: Thursday, March 18, 2004 8:03 AM Subject: Re: [wsbpel] Issue - 106 - ASSERT activity. > 1) Should an exception be thrown and potentially compensated, rather than > terminated ?? > 2) Should the assertion be attached to a "scope" level, rather than > activity level ?? > > Rgds, Ricky > > At 09:17 AM 3/18/2004 +0000, ws-bpel issues list editor wrote: > > >This issue has been added to the wsbpel issue list. The issues list is > >posted as a Technical Committee document to the > ><http://www.oasis-open.org/apps/org/workgroup/wsbpel>OASIS WSBPEL TC pages > >on a regular basis. The current edition, as a TC document, is the most > >recent document with the title in the "Issues" folder of the > ><http://www.oasis-open.org/apps/org/workgroup/wsbpel/documents.php>WSBPEL > >TC document list - the next posting will include this issue. The list > >editor's working copy, which will normally include an issue when it is > >announced, is available at > ><http://www.choreology.com/external/WS_BPEL_issues_list.html>this constant > >URL. > > > >Issue - 106 - ASSERT activity. > > > > > > > >Status: open > >Date added: 18 Mar 2004 > >Submitter: <mailto:mbs@fivesight.com>Maciej Szefler > >Date submitted: 18 March 2004 > >Description: I'd like to propose the addition of an assertion facility to > >the BPEL language. Specifically I'd like to see <precondition> and > ><postcondition> elements added to the list of standard elements, something > >along the lines of: > > > > <any-activity> > > <precondition> > > <expression language="XPath"> > > some-xpath-expression > > </expression> > > </precondition> > > <postcondition> > > <expression language="XPath"> > > some-xpath-expression > > </expression> > > </postcondition> > > > > > > > > .... > > > > > > > > </any-activity> > >Interpetation of the <pre-/post-condition> elements would be optional, but > >if assertions are enabled the expressions must evaluate to "true" or else > >the process instance is immediately terminated (ala <terminate>). > >Assertions would be available to both executable and abstract processes. > >-standard argument for assertions goes here-. > >Changes: 18 Mar 2004 - new issue > > > >---------- > >To comment on this issue, please follow-up to this announcement on the > >wsbpel@lists.oasis-open.org list (replying to this message should > >automatically send your message to that list), or ensure the subject line > >as you send it starts "Issue - 106 - [anything]" or is a reply to such a > >message. > > > >To add a new issue, see the issues procedures document (but the address > >for new issue submission is the sender of this announcement). > > > >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. > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]