Issue - 106 - ASSERT activity.

[ws-bpel issues list editor<peter.furniss@choreology.com>]

This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the 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 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 this constant URL.

Issue - 106 - ASSERT activity.

Status: open
Date added: 18 Mar 2004
Submitter: 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).