The genProject build descriptor option
places the output of Java™ generation
into a Workbench project and automates tasks that are required for Java runtime setup.
To use
genProject, specify the project
name. EGL then ignores the
buildPlan,
genDirectory,
and
prep build descriptor options, and preparation
occurs in either of two cases:
- Whenever you build the project.
- Whenever you generate the source files; but only if you selected
the workbench preference Build automatically.
To set this preference:
- Click to open the Preferences window.
- At the left side of the Preferences window, expand General and
click Workspace.
- Select the Build automatically check box
if you want EGL to build your files automatically. When you select
this preference, EGL performs a build whenever you save a file. This
means that EGL validates any parts of the file that have changed,
and any other parts in the project that are called by the changed
part. Validation is done without using a build descriptor part.
If you set the
genProject build descriptor
option to the name of a project that does not exist in the workbench,
EGL uses the name to create a Java project,
except when one of the following situations occurs:
- If you are generating a JSF Handler, it is always generated into
the project containing the related JSP file, regardless of the genProject build
descriptor option setting.
- A second exception concerns EJB processing
and occurs if you are generating a Java wrapper
when the linkage options part callLink element type property
is ejbCall (for the call from the wrapper
to the EGL-generated program). In that case, EGL uses the value of genProject to
create an EJB project and creates a new enterprise application project
(if necessary) with a name that is the same as the EJB project name
plus the letters EAR.
In addition to creating a project, EGL does as follows:
- EGL creates folders in the project. The package structure begins
within the project's Java Resources
folder.
When you are generating in the workbench, the following rules apply:
- For Java generation
- You are not required to specify either genProject or genDirectory.
If neither is specified, Java output
is placed in the project that contains the EGL source file being generated.
- For COBOL generation
- You must specify genDirectory, and in
most cases EGL ignores any setting for genProject.
If the COBOL program of type VGWebTransaction presents
a Web page, however, these statements apply:
- You may specify genProject, which indicates
a location for the associated Java-based objects that run in the Web
application server
- If you do not specify genProject, all
output is placed in the location identified in genDirectory
If you are generating from the EGL SDK, you may not use genProject.
Use genDirectory instead.