An EGL project includes zero to many source folders, each of which includes zero to many packages, each of which includes zero to many files. Each file contains zero to many parts.
An EGL project is formed by selecting EGL or EGL Web as the project type when you create a new project. You assign properties while working through the steps of project creation. To begin modifying your choices after you have completed those steps, right-click the project name and when a context menu is displayed, click Properties.
The value of this property is stored in a file named .eglpath in the project directory and is saved in the repository (if any) that you use to store EGL source files.
The EGL project wizards each create one source folder named EGLSource.
The value of this property is stored in a file named .eglpath in the project directory and is saved in the repository (if any) that you use to store EGL source files.
<?xml version="1.0" encoding="UTF-8"?> <eglpath> <eglpathentry kind="src" path="EGLSource"/> <eglpathentry kind="src" path="\AnotherProject"/> </eglpath>
The source folders for AnotherProject are determined from the .eglpath file in that project.
A package is a named collection of related source parts. The name is case sensitive: myPkg is different from MYPKG.
No package is in use when you create build parts.
By convention, you achieve uniqueness in package names by making the initial part of the package name an inversion of your organization's Internet domain name. For example, the IBM® domain name is ibm.com®, and the EGL packages begin with "com.ibm". By using this convention, you gain some assurance that the names of Web programs developed by your organization will not duplicate the names of programs developed by another organization and can be installed on the same server without possibility of a name collision.
com.mycom.mypack
c:\myWorkspace\new.project\EGLSource\com\mycom\mypack
The parts in an EGL source file all belong to the same package. The file's package statement, if any, specifies the name of that package. If you do not specify a package statement, the parts are stored directly in the source folder and are said to be in the default package. It is recommended that you always specify a package statement because files in the default package cannot be shared by parts in other packages or projects.
Two parts with the same identifier may not be defined in the same package. It is strongly recommended that you avoid using the same package name under different projects or different folders.
The package for generated Java output is the same as the EGL source file package.
Each EGL file belongs to one of these categories:
An EGL source file can include zero to many non-generatable parts but can include no more than one generatable part. The generatable part (if any) must be at the top level of the file and must have the same name as the file.
installationDir\egl\eclipse\plugins\ com.ibm.etools.egl_version
The file name (like egl_wssd_6_0.dtd) begins with the letters egl and an underscore. The characters wssd refer to Rational Web Developer and Rational Application Developer; the characters wsed refer to Rational Application Developer for z/OS®; and the characters wdsc refer to Rational Application Developer for iSeries™.
After you add parts to files, you can use a repository to maintain a history of changes.
This section gives recommendations for setting up your development projects.
For additional information, see Build descriptor part.
Related concepts
Build descriptor part
EGL services and Web services
Generation in the workbench
References to parts
Import
Introduction to EGL
Parts
Related reference
EGL build-file format
EGL source format
EGL statements