Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

Selecting XPath or XQuery for Expression Building

Selecting XPath or XQuery for Expression Building

The default language is XQuery, which is a superset of XPath. Process Developer projects contain an XQuery nature, including an XQuery editor for writing custom function XQuery modules.
The following table provides a brief comparison between XPath and XQuery as used in BPEL data mapping:
XPath
XQuery
Recommended if portability is an issue. Language is supported by WS-BPEL 2.0
Process Developer extension for BPEL
May be more suitable for multiple-part message variables
Builds large documents easily from a single-part variable
Limited to expression evaluation of one document node at a time
Allows manipulation of data from an entire XML document
Better at date handling, with many date functions
Location path expressions resolve to a string
Queries generate an XML result
Similar to a SQL-like query language. Easier to iterate over repeating elements with "FLWOR expressions" (FOR, LET, WHERE, ORDER BY, and RETURN) for performing joins
See also:

0 COMMENTS

We’d like to hear from you!