Output of Java program generation
The output of Java server program generation is as follows:
- A build plan, if the build descriptor option genProject is omitted
- Java source code (see Java program, page handler, and library)
- Related objects needed to prepare and run your program (see Java program, page handler, and library)
- J2EE environment file
- Program properties file
- A results file, if genProject is omitted
You can use the EGL generator to generate entire Java programs. Programs and records are generated as separate Java classes. Functions are generated as methods in the program. Data items and structure items are generated as fields of the record or program class to which they belong.
The following table shows the names of the various types of generated Java parts:
Names of generated Java parts
Part type and name What is generated Program named P A class named P in P.java Function named F in program P A method of the P class called $funcF in P.java Record named R A class named EzeR in EzeR.java Basic record named R, parameter to Function F A class named Eze$paramR in Eze$paramR.java Linkage options part named L Linkage properties file named L.properties Library named Lib A class named Lib in Lib.java DataTable named DT A class named EzeDT in EzeDT.java Form named F A class named EzeF in EzeF.java FormGroup named FG A class named FG in FG.java
- For the indicated part types, it is possible that two or more parts may exist with the same name. In that event the name of the second one will have an additional suffix, $v2. The name of the third will have a $v3 suffix, the fourth will have $v4, etc.
If the naming format would cause two names to be identical, EGL adds a suffix to each file generated after the first. The suffix as follows:
$vnwhere
- n
- Is an integer assigned in sequential order, beginning with 2.
Related concepts
Build plan
J2EE environment file
Java program, page handler, and library
Linkage properties file
Program properties file
Results file
Related reference
callLink element