EGL Reference Guide for iSeries
The next diagram shows the relationship of objects at run time.

Run-time events are usually as follows:
- To access a particular operation (as provided by a particular
EGL-generated program), a Web service client invokes a method of a local
proxy. The proxy is usually the output of a tool and can be based on
any computer language. The proxy is hereafter assumed to be an output
of the EGL Web Service Wizard and to be based on Java.
- The Java proxy has the same methods as the Web service Java bean and
includes the code necessary for these purposes:
- To transform the invocation data into XML
- To submit an XML message to the SOAP run-time code that resides on the
same machine as the Web service Java bean.
- The SOAP run-time code invokes the appropriate method of the Web service
Java bean, deserializing the client-side data from SOAP data types to Java
data types.
- The Web service Java bean accesses an EGL-generated program by
instantiating and invoking an EGL Java wrapper. This use of Java
wrappers is not specific to Web service processing and is described in
Java wrapper classes.
- The parameter data is returned to the Web service Java bean. If the
invoked EGL program returns two or more parameters, the Web service Java bean
instantiates and populates a Return Value Java bean so that the
(potentially changed) parameter data can be returned to the SOAP run time in a
single object.
- The Web service Java bean returns control to the SOAP run-time code, which
does these tasks:
- Serializes the server-side data from Java data types to SOAP data types
- Sends the serialized data to the client-side proxy, which returns control
to the Web service client
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.