Chapter 17 Working with WS-BPEL 2.0
The receive activity defines how the business process waits for a matching message to arrive. The receive activity supports the concept of implicit assignments using the element <fromParts>.
<receive name="ReceiveCreditInfo" partnerLink="CreditOrg" portType="cc:CheckCreditPT" operation="CheckCreditCallback"
variable="VCreditInfo" createInstance="no">
<correlations>
<correlation set="AccountKey" initiate="no"/>
</correlations>
</receive>
You design a receive activity in any of the following ways:
| Process property | Value |
|---|---|
| Implementation type | Execute operation |
| Action type | Receive request |
| Implemented by | Operation defined under a service provider within the same model |
| Received message | Input message of the operation |
| Message mapping | New variable with a message type |
The following extended attributes apply to the receive activity and are available from its property sheet:
| Name | Internal code | Description |
|---|---|---|
| Create Instance | CreateInstance | Instantiates the process |
| Initiate Correlation | InitiateCorrelation | When a correlation is used by the receive activity the initiate attribute can be yes, no or join |
| Join Condition | joinCondition | Join condition |
| Suppress Join Failure | suppressJoinFailure | Avoids propagation of Join Failure exceptions |
| — | MultipleCorrelation | Defines BPEL Invoke, Receive or Reply activities using several correlations. |
| — | expressionLanguage | Specifies the expression language used in expressions |
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |