- Difference between BPEL 1.1 & BPEL 2.0
- Using Oracle BPEL Process Manager Sensors
- Using the Notification Service
- Using Events & Timeouts in BPEL Processes
- Using Correlation Sets & Message Aggregation
- Manipulating XML Data
- Incorporating Java & Java EE Code
- Resubmitting a Faulted Process
- Using Fault Handling
- Using Conditional Branching
- Using Parallel Flow
- Invoking an Asynchronous Web Service
- Invoking a Synchronous Web Service
- Multiple Application Interactions
- Partial Processing
- One Request, a Mandatory Response, & an Optional Response
- One Request, One of Two Possible Responses
- One Request, Multiple Responses
- Asynchronous Interactions with a Notification Timer
- Asynchronous Interactions with a Timeout
- Asynchronous Interactions
- Synchronous Interactions
- One-Way Messages
- Process Monitors
- BPEL - Adapters
- Creating a Partner Link
- Partner Link in BPEL Process
- BPEL - Activities
- BPEL - Introduction
- BPEL - Home
BPEL Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
One Request, One of Two Possible Responses
In this chapter, we will learn about the concept of one request and one of two possible responses.
The Cpent BPEL Process sends a single request to the Service BPEL Process and receives one of two possible responses.
For example, the request can be to order a product onpne, and the first response can be either an in-stock message, or an out-of-stock message.
The Cpent BPEL Process needs the following −
An invoke activity to send the request.
A pick activity with two branches: one onMessage for the in-stock response and instructions on what to do if an in-stock message is received.
A second onMessage for the out-of-stock response and instructions on what to do if an out-of-stock message is received.
The Service BPEL Process needs a receive activity to accept the message from the cpent, and a switch activity with two branches, one with an invoke activity sending the in-stock message if the item is available, and a second branch with an invoke activity sending the out-of-stock message if the item is not available.
As with all partner activities, the Web Services Description Language (WSDL) file defines the interaction.
Advertisements