EGL Reference Guide for iSeries

A deployment consideration

If an EGL-generated program in a Web service includes an EGL record or structure as a parameter, the implications are as follows:

If the Java proxy uses a combination of BeanInfo and parameter wrapper class for a given parameter, those classes are copies of the classes that are used by the SOAP run-time code.

If the Web service client runs on the same machine as the Web service Java bean, the complexities of the technology can result in run-time errors unless you follow a simple rule: Always maintain the Java proxy in a package different from that of the Web service Java bean. You can easily fulfill this rule because the EGL Web Service Wizard allows you to create a client project.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]