In scenarios in which the repeating structure is of smaller payloads compared to the overall payload size, Oracle recommends using XSLT transformations because the current XSLT implementation materializes the entire DOM in memory. For example, use PurchaseOrder.LineItem.Supplier (a subpart of a large payload).

You can also substitute it with the assign activity, as it performs a shadow copy. Although a shadow copy does not materialize DOM, it creates a shadow node to point to the source document.

You can also use the following optimized translation functions while performing transformations/translations of large payloads:

• ora:doTranslateFromNative or med:doTranslateFromNative

• ora:doTranslateToNative or med:doTranslateToNative

• ora:doStreamingTranslate or med:doStreamingTranslate

For more information about these functions, see XPath Extension Functions and Understanding Technology Adapters.