My Oracle Support Banner

Call Using REST Adapter In BPEL Does Not Work (Doc ID 2568059.1)

Last updated on MAY 15, 2020

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, Technology Adapters

ACTUAL BEHAVIOR
---------------
Call using REST Adapter in BPEL does not work

When calling from a BPEL (BPEL A) using a REST Adapter another BPEL (BPEL B) that is exposed also via REST Adapter we are getting an error.
BPEL A is working with native JSON, using the default option of the REST Adapter not to convert to XML
BPEL A is working with xml, using the option of the REST Adapter to convert to XML

When BPEL A calls BPEL B we have observed that the Fusion adds an <input> tag to the payload. However, when we point the same BPEL A to another end point (for example in APIary), Fusion does not add that <input> tag. Looks like somehow when the call is from BPEL A to BPEL B, the data leaving BPEL A is not the same as if BPEL A were to call something not Fusion.



EXPECTED BEHAVIOR
-----------------------
For the xml output to be same as native json

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.