invocation style

You can define the invocation style of a service as "document" or "RPC" , and the encoding can be "SOAP" or "literal" .

In the request-response invocation style, a client service invokes an operation that happens to be implemented through rules.

This introduces a significant point: When a service is designed, what determines the invocation style to be used?

In other words, the design decisions on invocation style and strong typing of an interface have little, if anything, to do with each other.

If the reference is w-typed then the only invocation style available to the user is DII.

Whether the invocation style is synchronous request response or asynchronous message based.

Like BPEL, interface maps always use the invokeAsyncWithCallback invocation style for asynchronous request-response invocations.

In this case, the callout node invocation will also be made using invokeAsyncWithCallback invocation style.

The invocation style used by SCA exports and Standalone References depends on the style used by the invoker.

As above, all asynchronous invocations are made using the async with callback invocation style, never asynchronous deferred response.

All asynchronous invocations are made using the invokeAsyncWithCallback invocation style, never asynchronous deferred response.

This is a typical invocation style in an SOA environment with messaging middleware.

Approach 1 enables a lightweight client invocation style, while Approach 2 makes the service implementation fairly simple.

Asynchronous: Indicates the preferred invocation style is either asynchronous with deferred response or asynchronous with callback

Special behaviour of the invocation style within a Fan Out or Fan In primitive

Invocation style depends on the source component