The
build descriptor option secondaryTargetBuildDescriptor specifies
a build descriptor that guides the generation of code being deployed to a
Web application server, while other code (which is targeted for other environments)
is being generated in the same generation request.
Each of the following situations is of interest:
- You are generating a VGWebTransaction program with build descriptor option genVGUIRecords set
to YES so that both the program (destined to run outside of a Web application
server) and the VGUIRecords referenced by that program are generated
- You are selecting a project for generation when the EGL source folder
contains the following parts, which may be in different packages:
- PageHandlers to be deployed to a Web application server
- Programs that the PageHandlers call from a platform that is outside of
a Web application server
If you wish to use one build descriptor to control generation of two sets
of parts, do this:
- Establish options for the parts that are not deployed to the Web application
server
- Assign a value to the option secondaryTargetBuildDescriptor for
the parts that are deployed to the Web application server.
In cases like those described earlier,
secondaryTargetBuildDescriptor can
reference a build descriptor to use when you generate the following output:
- VGUIRecords
- PageHandlers
- A message table that is produced during generation of a VGWebTransaction
program
- A table that is used for validating VGUIRecord data, when the table is
produced during generation of a VGWebTransaction program
You can set any options in the build descriptor named in
secondaryTargetBuildDescriptor,
but only the following have an effect:
- destDirectory
- destHost
- destPassword
- destPort
- destUserID
- genDirectory
- genProject
- genResourceBundle
- msgTablePrefix
- resourceBundleLocale
- system
- targetNLS
- tempDirectory