1. Developing SOA Applications with Oracle SOA Suite
  2. Using Binding Components
  3. Using Direct Binding to Invoke Composite Services
  4. Invoking a SOA Composite Application in Oracle JDeveloper with the Invocation API

Invoking a SOA Composite Application in Oracle JDeveloper with the Invocation API

The Direct icon in the Components window in Oracle JDeveloper, as shown in Figure 39-3, provides support for exchanging SOA messages with SOA over RMI.

Figure 39-3 Direct Binding Option

Description of Figure 39-3 follows
Description of "Figure 39-3 Direct Binding Option"

Oracle JDeveloper supports creating a direct service binding and a direct reference binding that invokes either an Oracle Service Bus or another SOA composite.

Note:

For a client to invoke composite services over direct binding, its class path must include both soa-infra-mgmt.jar, wlthint3client.jar, and oracle-soa-client-api.jar.

For more information about the Direct Binding Invocation API, see Introduction to the Direct Binding Invocation API.