Generating OO Source Files from an OOM

PowerDesigner provides a standard interface for generating source files for all the supported OO languages. For details of language-specific options and generation tasks, see the appropriate language chapter.

1. Select Language > Generate langage Code to open the Generation dialog box:
   
   
   
2. Enter a directory in which to generate the files, and specify whether you want to perform a model check (see Checking an OOM).
3. [optional] Select any additional targets to generate for. These targets are defined by any extensions that may be attached to your model (see Working with Generation Targets).
4. [optional] Click the Selection tab and specify the objects that you want to generate from. By default, all objects are generated, and PowerDesigner remembers for any subsequent generation the changes you make.
   
   
   
5. [optional] Click the Options tab and set any necessary generation options. For more information about these options, see the appropriate language chapter.
   Note: For information about modifying the options that appear on this and the Tasks tab and adding your own options and tasks, see Customizing and Extending PowerDesigner > Object, Process, and XML Language Definition Files > Generation Category.
6. [optional] Click the Generated Files tab and specify which files will be generated. By default, all files are generated.

   For information about customizing the files that will be generated, see Customizing and Extending PowerDesigner > Extension Files > Generated Files (Profile).

7. [optional] Click the Tasks tab and specify any additional language-specific generation tasks to perform.
8. Click OK to begin generation.

   When generation is complete, the Generated Files dialog opens, listing the files that have been generated to the specified directory. Select a file in the list and click Edit to open it in your associated editor, or click Close to exit the dialog.

• Working with Generation Targets
  The Targets tab of the Generation dialog box allows you to specify additional generation targets, which are defined by extension files.
• Defining the Source Code Package
  For those languages that support the concept of packages and/or namespaces, classes must be generated in packages that are used as qualifying namespace. You can define these qualifying packages one by one in the model as necessary, or insert a base structure automatically via the Add Package Hierarchy command.