Overview of Java generation

This section provides Java-specific information related to generating Java™ for any of the Java environments, including iSeries®. This topic includes an overview of Java generation; other topics in this section include the following information:

Generation takes place automatically whenever you save a generatable part. This automated process consists of two phases:

Validation for the target runtime environment
The validation phase comes first. Here are the required input parts for the validation phase:
  • The generatable part, such as program, library, or JSF handler.
  • The Build Descriptor part, which provides the following:
    • The target runtime environment, which is specified in the system build descriptor option.
    • The name of the linkage options part, if any, as specified in the linkage build descriptor option
    • The name of the resource associations part, if any, as specified in the resourceAssociation build descriptor option
    • A subset of build descriptor options that are used during the validation phase, such as the validateSQLStatements build descriptor option.
The validation done at generation time is specific to the target runtime environment. EGL performs the following actions during this validation:
  • Verifying that the source code is compatible with the target runtime environment.
  • Verifying that the entries in the linkage options part and the resource associations part are correct based on the target runtime environment.
  • Performing any special validation required, such as that requested with the validateSQLStatements build descriptor option.
Production
During this phase, the EGL generatable parts are generated into Java source code. This phase requires the following inputs:
  • Validated EGL source code.
  • All build descriptor options, including those validated in validation phase.
  • Linkage options parts
  • Resource association parts
  • Other information such as the Java runtime properties set in the Build Descriptor part.
After generation, the output resulting from this phase consists of the following:
  • Java source code
  • Additional output based on the type of part being generated and the specific build descriptor options that are set.
Any error messages are shown in the EGL Generation Results view.

Once you have successfully generated all the code for your application, you can deploy it to the environment where it runs; see Deploying EGL applications


Feedback