Chapter 2 Resource Files and the Public Metamodel
All extended model definitions have the same basic category structure. The root node of each file contains the following properties:
| Property | Description |
|---|---|
| Name | Specifies the name of the extended model definition. This name must be unique in a model for generic or specific XEMs. |
| Code | Specifies the code of the extended model definition. This code must be unique in a model for generic or specific XEMs. |
| File Name | [read-only] Specifies the path to the extended model definition file. If the XEM has been copied to your model, this field is empty. |
| Family | Restricts the availability of the XEM to a particular target family. For example, when an XEM has the family Java, it is available only for use with targets in the Java object language family. |
| Subfamily | Refines the family. For example, 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 Extended Model Definition Selection window. For example, a category called "Application Server" is used to group all server XEMs. Extended model definitions having the same category cannot be generated simultaneously. If you do not define 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. Before starting the generation, click the Preview page of the relevant object, and hit the Refresh tool to display these templates.
When you double-click on a trace line from the Preview page, the Resource Editor opens to the corresponding template definition in the Profile\Object\Templates category. |
| Complement language generation | Specifies that the XEM is used to complement the generation of an target language. The generation items of the object language are merged with those of the XEM before generation. All generated files specified in the target resource file and any attached XEMs are generated. If two generated files have identical names, the file in the XEM overrides the one defined in the target.
Note that PowerBuilder does not support XEMs for complementary generation. |
| Comment | Provides a descriptive comment for the XEM. |
| Copyright (C) 2008. Sybase Inc. All rights reserved. |
| |