How Can URI Parameters Be Mapped When The Payload Also Needs To Be Passed Using The REST Adapter, And Not See This Error - oracle.fabric.common.FabricInvocationException: java.lang.IllegalArgumentException: loadID (Doc ID 2261138.1)

Last updated on MAY 05, 2017

Applies to:

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

Goal

There is a business need to invoke a REST service with the POST operation, and an URL such as http://server:host/api/v1/tracking/{loadID}/{truckid} and pass a JSON payload. In order to do this, these are the steps that were followed:

  - Use the REST Adapter to configure the REST service with template URL parameter loadID and truckid, and also configure the Request/Response Schema.
  - Connect the REST Adapter service inside a BPEL Process for invocation.
  - While mapping in the BPEL process, only payload fields are visible for mapping, and the URI template parameters are not part of the XSD/WSDL created automatically as part of REST Adapter configuration.
  - If only the payload fields are mapped, and the service deployed, the below error is seen:

<part name="summary">
<summary>oracle.fabric.common.FabricInvocationException: java.lang.IllegalArgumentException: loadID</summary>
</part>

How can the URI parameters be mapped, when the payload also needs to be passed?
 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms