The generated Java proxy is a set of object-oriented classes that correspond to the set of methods selected during generation. There are three main classes that a developer can use and access. Other classes are generated, but they are not exposed for use by the application. The three exposed classes are:
The details of the three generated interfaces are discussed later in this chapter.
In addition to the generated interface, the Java Proxy also consists of runtime code and a set of user modifiable exit routines. The user exits influence how the runtime handles security and communications processing. This chapter discusses the Java Proxy user exits.
The creation of an executable Java Proxy involves both generating the Java Proxy source code and installing the proxy. You can choose to do these two operations as two independent activities or as a single operation (check Install after generation option on the Proxy Code Generation dialog).
Generating a Java Proxy results in a \proxy\java directory being added within your <model-name>.ief directory. All proxy code is contained in a series of directories beneath \proxy\java.
Note: The Java Proxy and the Classic Style Java Proxy both generate into the \proxy\java directories and overwrite each other if the names are the same.
After the Build Tool has successfully built the proxy, the \proxy\java directory includes a \deploy\<component> directory, which includes a \samples directory. Within the \samples directory are directories for \APP, \JSP, and \XML. Select the optional XML API only if you want to generate the XML sample. The \JSP, \APP, and \XML directories contain generated samples to test the proxies and demonstrate possible usages of the proxy. The samples are not considered part of the proxy itself.
If you select XML API for generation, then the \deploy\<component> directory also includes the XML schema file (.XSD). The XML schema file is considered part of the proxy itself.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|