Chapter 4 Extending your Models with Profiles
You define a transformation profile using the following properties:
| Property | Description |
|---|---|
| Name | Name of the transformation profile |
| Comment | Additional information about the transformation profile |
| Model Type | [optional] Specifies the type of model with which the transformation profile can be used. This is a way to filter profiles during generation. For example, if you select OOM when the current extended model definition is in a PDM, the transformation profile can be used during PDM to OOM generation or reverse engineering |
| Family and subfamily | [optional] If the model type supports a target resource file, you can also define a family and subfamily to filter the display of profiles in the generation dialog box. The family is used to establish a link between the resource file of a model and an extended model definition. When the resource file family corresponds to the extended model definition family, it suggests that the extended model definition complements the resource file |
| Pre-generation | The Pre-generation tab lists the transformations to be executed before model generation. These transformations are executed when the current model in which you have created the extended model definition is the source model, and when the constraints defined in the model type, family, and subfamily boxes are met.
Any object created during pre-generation is automatically added to the list of objects used in generation. These changes to the source model are temporary and are reversed after generation is complete. For example, you can define a transformation profile with a transformation that cancels the creation of EJBs from classes before generating an OOM into a PDM in order to establish a better mapping between classes and tables during generation. |
| Post-generation | The Post-generation tab lists the transformations to be executed after generation. These transformations are executed when the current model in which you have created the extended model definition is the target model.
For example, you can define a transformation profile with a transformation that automatically applies the correct naming conventions to the generated model. |
| Copyright (C) 2008. Sybase Inc. All rights reserved. |
| |