Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Disable bpel selectionFailure Fault Example

Disable bpel selectionFailure Fault Example

The following example shows the effect of enabling and disabling the
Disable bpel:selectionFailure Fault
(BPEL4WS 1.1 processes:
bpws:selectionFailure
) option.
For details on WS-BPEL 2.0 processes, see
Using the Process Developer Disable Selection Failure Fault Extension
.
For a description of this BPEL4WS 1.1 preference, see
Simulation Preferences
.
Code sample:
<assign> <copy> <from part="OrderInfo" query="/ns1:OrderInfo /ns1:OrderHeader/ns1:BillToInfo/ns1:Addr1" variable="var1"/> <to part="OrderInfo" query="/ns1::Addr1" variable="var2"/> </copy> </assign>
In the code sample, the
Assign From/To
query is for an optional element, as shown in the schema snippet below.
Schema Snippet for Var1 and Var2
:
<xs:complexType name="AddressInfoType"> <xs:sequence> <xs:element ref="ord:Name"/>
<xs:element ref="ord:Addr1" minOccurs="0"/>
<xs:element ref="ord:Addr2" /> <xs:element ref="ord:City"/> <xs:element ref="ord:St"/> <xs:element ref="ord:Zip"/> <xs:element ref="ord:Cntry" /> </xs:sequence> </xs:complexType> <xs:element name="BillToInfo" type="ord:AddressInfoType"/>
Var1 Sample Data
Var2 Initialization
<ns1:OrderInfo xmlns:ns1="http://temp.com"> <ns1:OrderHeader> <ns1:OrdId>78</ns1:OrdId> <ns1:BillToInfo> <ns1:Name>Name1</ns1:Name>
(Addr1 is missing)
<ns1:Addr2>1 Main St </ns1:Addr2> <ns1:City>Albany</ns1:City> <ns1:St>NY</ns1:St> <ns1:Zip>12012</ns1:Zip> <ns1:Cntry>USA</ns1:Cntry> </ns1:BillToInfo> ...
<ns1:OrderInfo xmlns:ns1="http://temp.com"> <ns1:OrderHeader> <ns1:OrdId/> <ns1:BillToInfo> <ns1:Name/>
<ns1:Addr1/>
<ns1:Addr2/ <ns1:City/> <ns1:St/> <ns1:Zip/> <ns1:Cntry/> </ns1:BillToInfo> ...
With
Disable bpel:selectionFailure Fault
disabled
, the simulation ends in a Selection Failure fault because
Var1
is missing the query selection node, and it cannot be assigned to the
Var2
query selection node.
With
Disable bpel:selectionFailure Fault
enabled, the process terminates normally because the empty selection node is allowed. A null value is added to
Addr1
during the assignment.


Updated March 30, 2020