Accessing an EGL service in either of its two forms

If the logic for a given service is written in EGL, the logic might be accessed as a dedicated service or as an EGL REST-RPC service. In that second case, the service is deployed outside of the Rich UI application, typically on a different server.

Here is the simplest way to switch between accessing the identical EGL service logic in one way or another:

In your code, declare a binding variable and embed it in a call statement.

In the EGL deployment descriptor, define an entry. To switch between the two forms of the same service logic, you can vary the entry in the same deployment descriptor or, more likely, can reference a different deployment descriptor with a same-named entry.

Accessing a third-party REST service

A Rich UI handler can invoke a proxy function, which must be in a package that is generated to JavaScript. The proxy function requires no logic at all: your access to the service is based on setting values in function annotations and in a deployment-descriptor entry.

The example in this section shows how to invoke a third-party REST service; specifically, the service that is described here: Airport status