Assertions Tab

2.34 Assertions Tab

Use to specify an assertion condition that is executed upon receipt of a callback message in request-response invoke activities, receive activities, and onMessage branches of pick activities.

For reply and preassert invoke activities, the condition executes before performing the activity. If the condition evaluates to true, the invoke activity executes. For receive, onMessage, and postassert invoke activities, the condition executes upon receipt of a callback message. The invoke activity executes before the assert activity. Essentially, it is used to assert the inbound message.

The assertion specifies an XPath expression that, when evaluated to false, causes a BPEL fault to be thrown from the activity. This condition provides an alternative to creating a potentially large number of switch, assign, and throw activities after a partner callback. If no fault is specified in the Assertions tab, it defaults to AssertFailure. Otherwise, it throws the fault declared in the Assertions tab.

The bpelx:assert extension specifies the XPath expression to evaluate upon receipt of a callback message from a partner. If the assertion expression returns a false boolean value, the specified fault is thrown from the activity. If the assertion expression returns a true boolean value, no fault is thrown and the activities following the invoke activity, receive activity, or onMessage branch of a pick or scope activity are executed as in a normal BPEL process flow.

Element	Description
Pre Asserts Tab (BPEL 2.0 projects only)	Displays the defined preassertion conditions. Click this tab, then click Add to create a preassertion condition.
Post Asserts Tab (BPEL 2.0 projects only)	Displays the defined postassertion conditions. Click this tab, then click Add to create a postassertion condition.
Add Icon	Click to create an assertion condition. In BPEL 1.1 projects, the following options appear: Pre Assert: If selected, the condition is executed before the invoke or reply activity sends out the outbound message. Post Assert: If selected, the condition is executed after the invoke activity, receive activity, or onMessage branch receives the inbound message. In BPEL 2.0 projects, no Pre Assert or Post Assert options are displayed. To create a preassertion condition, you must first select the Pre Asserts tab. To create a postassertion condition, you must first select the Post Asserts tab.
Edit Icon	Click this tab, then click Add to edit a selected assertion condition.
Delete Icon	Click to delete a selected assertion condition.
Assertions	Displays details about the created assertions, including the name, type (preassert or postassert), XPath expression, fault to be thrown, and message.