You can specify a UML model, component, package that contains components, or a combination of these elements as the source of the UML-to-CORBA transformation. The transformation generates a single IDL file for each UML component in the hierarchy of the specified source. Each IDL file contains code only for the elements that the corresponding UML component owns. The transformation ignores elements that are not owned by a UML component. If you specify any other element as the source for the transformation, the transformation fails during validation.
When you apply the CORBA transformation profile, you can specify the UML components that are transformed into CORBA IDL elements by setting the generateCode property to true or false. During code generation, the transformation ignores components that have the generateCode property set to false.
The transformation generates an #include directive when a type definition is in a different component. Most CORBA IDL files must include the ORB.IDL file. To force an #include directive in a generated IDL file of an external IDL file that you have not modeled, you must create a dependency from the component to a component that represents the external IDL file. If you do not want the transformation to generate code for the component that represents the external IDL file, you can set the generateCode property to false.
The UML-to-CORBA transformation can output files to an Eclipse project. The project contains the IDL file or files, which are considered Eclipse workspace resource files. Generated files are displayed in the Java perspective in the Navigator view and the Package Explorer view.
The UML-to-CORBA transformation supports models that contain cross-model references. For example, Interface A in the current model could extend Interface B from another model. The transformation creates an #include directive for the IDL file in which the used type appears; in this example, the transformation creates an #include directive in Interface B. The transformation does not manage the location of the included IDL files in the file system. You should maintain the relative paths of the generated IDL files by creating a mapping model.