Creating REST Support in Service and Reference Binding Components
Oracle SOA Suite components, services, and references can be selected and exposed as a REST service. This section describes:
- How to Configure the REST Binding Component in a SOA Composite Application
- How to Consume REST-Based Integrations Created in Oracle Integration from SOA Composite Applications
- How to Configure the REST Adapter Through Shortcuts
- How to Generate Schemas Manually
- How to Generate Schemas from Samples
- How to Use Global Token Variables
- How to Set REST Header Properties
- What You May Need to Know About REST Fault Binding
- What You May Need to Know About Converting a JSON Interchange Format to a REST Schema
- What You May Need to Know About REST References Calling REST Services in the Same Node
Note:
-
Follow Java naming conventions for query, path, and template parameter names while creating Inbound REST bindings (REST service). A REST reference does not require any naming conventions as runtime does not create a Java stub for REST references (outbound REST binding).
-
You cannot attach a REST binding to an asynchronous component (for example, an asynchronous BPEL process). If you attempt this attachment, a message is displayed that indicates this is not supported and suggests a workaround of placing an Oracle Mediator between the REST adapter and the service that has a one-way interface and routing the service callback to another (outbound) REST adapter service.
-
You cannot connect a REST service binding component to a REST reference binding component.