SOA Ecosystem–Interconnected Principles, Patterns, and Frameworks - Applied SOA Patterns on the Oracle Platform - page 70

◦ Correlations and correlations sets, which include native support for long
running processes. Native transition for different protocols, that is,
SOAP/HTTP <->JMS .
◦ Implicit Correlation support.
◦ Support of standard BPEL Faults, the ability to assign recovery opera-
tions dynamically or statically, and fault handling in long-running com-
positions using compensations.
◦ Custom activity implementation and custom variable assignment exten-
sions. BPEL 2.0 extensibility mechanism implementation.
◦ Embedded Java support (or any other high-level language).
◦ Level of XPath support (XPath versions).
◦ SOAP/Message Header support, that is, the ability to reassign the whole
header to the new message.
◦ Level of XQuery support (XQuery version).
◦ Level of REST support in BPEL. Native support REST and SOAP re-
sources (partner links).
◦ The forEach looping and branching support for the XML nodes with
various interactions technique.
◦ Assigning data by default to the missing/empty nodes.
◦ Supporting transport and message processing metadata (Message Track-
ing Data or Process context metadata).
◦ SBDH support (optionally).
◦ Dynamic partner links invocation.
◦ Rule-based invocation/mediation. Limitations for MEPs and data trans-
formation.
◦ Orchestration engine's capability to clean-up orphan/obsolete data in hi-
bernation store automatically or by schedule.
◦ Transformation accelerators, partial validation.
◦ Transport protocol accelerators.
◦ Possibility to use external transformation engines for complex callouts in
transformation.
◦ Runtime optimization of message size in order to avoid possible memory
leak.
◦ Various compensation flows implementation technique.
◦ Possibility to dynamically invoke different compensation flows by rules/
types of failures.
◦ Asynchronous Service Broker implementation.
◦ WSIF support (implementations, extensions).