Introduction to Interface parts

You can use interface parts to access a remote service, such as a Web service.

In situations where you want to restrict access to the source code, you can also use an Interface part to access a local service. For example, you might ship services as generated Java™ classes with EGL Interface parts so that the customer can invoke the services from EGL programs. For information on Interface part syntax, see Interface part.

The Interface part includes a set of function prototypes (see Function prototypes). Each prototype has an ending semicolon (;) and includes only a function name, parameter list, and return type:
  Interface StockQuote
    Function getQuote(symbol String in) returns (float);
  end

You cannot use an Interface part directly in your code; you must create a variable that is based on the part. At run time, the variable refers to a service that you are running from a specific location (URI).

When you access a service through an interface, the interface must be bound to the location of the service implementation with a deployment descriptor file. The deployment descriptor file describes how other applications can use a Service part from your application, and how your application uses an external service. For more information, see the EGL Generation Guide.

Uses of interface parts


Feedback