All extension files have the same basic category structure.
The root node of each file contains the following properties:
|
Property |
Description |
|---|---|
|
Name / Code |
Specify the name and code of the extension file, which must be unique in a model. |
|
File Name |
[read-only] Specifies the path to the extension file. If the XEM has been copied to your model, this field is empty. |
|
Family / Subfamily |
Restricts the availability of the XEM to a particular target family and subfamily. For example, when an XEM has the family Java, it is available only for use with targets in the Java object language family. EJB 2.0 is a sub-family of Java. |
|
Auto-attach |
Specifies that the XEM will be automatically attached to new models with a target belonging to the specified family. |
|
Category |
Groups XEMs by type for generation and in the Select Extensions dialog. Extensions having the same category cannot be generated simultaneously. If you do not specify a category, the XEM is displayed in the General Purpose category and is treated as a generation target. |
|
Enable Trace Mode |
Lets you preview the templates used during generation (see Templates (Profile)). Before starting the generation, click the Preview page of the relevant object, and click the Refresh tool to display the templates. When you double-click on a trace line from the Preview page, the Resource Editor opens to the corresponding template definition. |
|
Complement language generation |
Specifies that the XEM is used to complement the generation of an DBMS or language definition, so that items to be generated for the language are merged with those of the XEM before generation, and all generated files specified by both the language definition and the XEMs are generated (see Generated Files (Profile)). If two generated files have identical names, the file in the XEM overrides the one defined in the target. Note: PowerBuilder does not support XEMs for
complementary generation.
|
|
Comment |
Provides a descriptive comment for the XEM. |