- BPEL - Home
- BPEL - Introduction
- BPEL - Activities
- Partner Link in BPEL Process
- Creating a Partner Link
- BPEL - Adapters
- Process Monitors
- One-Way Messages
- Synchronous Interactions
- Asynchronous Interactions
- Asynchronous Interactions with a Timeout
- Asynchronous Interactions with a Notification Timer
- One Request, Multiple Responses
- One Request, One of Two Possible Responses
- One Request, a Mandatory Response, & an Optional Response
- Partial Processing
- Multiple Application Interactions
- Invoking a Synchronous Web Service
- Invoking an Asynchronous Web Service
- Using Parallel Flow
- Using Conditional Branching
- Using Fault Handling
- Resubmitting a Faulted Process
- Incorporating Java & Java EE Code
- Manipulating XML Data
- Using Correlation Sets & Message Aggregation
- Using Events & Timeouts in BPEL Processes
- Using the Notification Service
- Using Oracle BPEL Process Manager Sensors
- Difference between BPEL 1.1 & BPEL 2.0
BPEL - Resubmitting a Faulted Process
In this chapter, we will see different scenarios related to the resubmitting of a faulted process.
Scenario A
The BPEL code uses a fault-policy and a fault is handled using the ora-human-intervention activity. The fault is then marked as Recoverable and the instance state is set to Running.
Scenario B
The BPEL code uses a fault-policy and a fault is caught and re-thrown using the ora-rethrow-fault action. The fault is then marked as Recoverable and the instance state is set to Faulted; provided the fault is a recoverable one (like URL was not available).
Advertisements