InvokeRegistry.TIntfInvokeOption Enumeration

TIntfInvokeOption and TIntfInvokeOptions represent flags that customize how to handle calls to an invokable interface.

Pascal

TIntfInvokeOption = (
  ioDefault,
  ioDocument,
  ioLiteral,
  ioHasDefaultSOAPAction,
  ioHasReturnParamNames,
  ioHasNamespace,
  ioIsAppServerSOAP,
  ioHasUDDIInfo,
  ioHasAllSOAPActions
);

C++

enum TIntfInvokeOption {
  ioDefault,
  ioDocument,
  ioLiteral,
  ioHasDefaultSOAPAction,
  ioHasReturnParamNames,
  ioHasNamespace,
  ioIsAppServerSOAP,
  ioHasUDDIInfo,
  ioHasAllSOAPActions
};

File

InvokeRegistry

Description

TIntfInvokeOptions is a set of TIntfInvokeOption values. TIntfInvokeOption values are flags that can be registered with an invokable interface to indicate how it should be called. The following table lists the possible values.

Value	Meaning
ioDefault	Calls to the interface use the default options unless overridden by other options. (RPC-based SOAP encoding and HTTP as a transport protocol).
ioDocument	The Web Services server uses document-style encoding.
ioLiteral	The Web Services server uses document-literal style and the types for input and output values have not been unwound to create a method call.
ioHasDefaultSOAPAction	A default SOAP action header has been registered for use with the interface.
ioHasReturnParamNames	A set of parameter names have been registered for use with the interface that are reserved for the return value of function calls. If this option is not set, the strings 'Return' and 'Result' are used.
ioHasNamespace	A namespace was explicitly provided when the interface was registered, rather than using an automatically-generated namespace.
ioIsAppServerSOAP	The interface descends from IAppServerSOAP. Such interfaces are used in multi-tier database applications to interact with the application server.
ioHasUDDIInfo	UDDI information has been registered for the interface. This option is set when the Web Service description is imported using the UDDI browser.
ioHasAllSOAPActions	The SOAPAction headers could not be collapsed into a single string. When representing the SOAP action headers, a single string is created where the first character represents a delimiter that marks the boundary between the various SOAP action headers.

What do you think about this topic? Send feedback!