The meaning of locale is described at the end of this section.
The meaning of locale is described at the end of this section.
The meaning of locale is described at the end of this section.
The meaning of locale is described at the end of this section.
You must customize the name of the property itself when you specify a substitution value for SN, at deployment time. The substitution value in turn must match either the server name that is included in the invocation of VGLib.connectionService or the database name that is included in the invocation of sysLib.connect.
Your system administrator may require that you use a master build descriptor to specify information that cannot be overridden and that is in effect for every generation that occurs in your installation of EGL. By a mechanism described in Master build descriptor, the system administrator identifies that part by name, along with the EGL build file that contains the part.
If the information in the master build descriptor is not sufficient for a particular generation process or if no master build descriptor is identified, you can specify a build descriptor at generation time, along with the EGL build file that contains the generation-specific part. The generation-specific build descriptor (like the master build descriptor) must be at the top level of an EGL build file.
You can create a chain of build descriptors from the generation-specific build descriptor, so that the first in the chain is processed before the second, and the second before the third. When you define a given build descriptor, you begin a chain (or continue one) by assigning a value to the build descriptor option nextBuildDescriptor. Your system administrator can use the same technique to create a chain from the master build descriptor. The implication of chaining information is described later.
Any build part referenced by a build descriptor must be visible to the referencing build descriptor, in accordance with the rules described in References to parts. The build part can be a linkage options part or a resource associations part, for example, or the next build descriptor.
Default options can be useful when your organization develops a set of programs that must be generated or prepared similarly.
If a given build descriptor is used more than once, only the first access of that build descriptor has an effect. Also, only the first specification of a particular option has an effect.
Let's assume that the master build descriptor contains these (unrealistic) option-and-value pairs:
OptionX 02 OptionY 05
In this example, the generation-specific build descriptor (called myGen) contains these option-and-value pairs.
OptionA 20 OptionB 30 OptionC 40 OptionX 50
As identified in myGen, the next build descriptor is myNext01, which contains these:
OptionA 120 OptionD 150
OptionB 220 OptionD 260 OptionE 270
As identified in the master build descriptor, the next build descriptor is myNext99, which contains this:
OptionZ 99
EGL accepts option values in the following order:
OptionX 02 OptionY 05
Those options override all others.
OptionA 20 OptionB 30 OptionC 40
The value for optionX in myGen was ignored.
OptionD 150 OptionE 270
The value for optionA in myNext01 was ignored, as was the value for optionD in myNext02.
OptionZ 99
Related concepts
Build
Java runtime properties
References to parts
Master build descriptor
Parts