The UML-to-CORBA transformation generates Common Object Request Broker Architecture (CORBA) Interface Definition Language (IDL) from Unified Modeling Language (UML) model elements.
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.
The following table lists how the UML-to-CORBA transformation generates CORBA IDL from UML model elements.
UML model element | CORBA element |
---|---|
Component | IDL file |
Primitive types | Basic types, native types |
Package | Module (if the package is in a component) |
Interface | Interface |
Attribute or association | Attribute |
Operation | IDL operation |
Parameter | Parameter of the IDL operation |
Enumeration | Enumeration |
Class <<CORBAvalue>> | Value type, custom value type, boxed value type |
Static attribute | Constant |
Class <<CORBAStruct>> | Struct |
Class <<CORBAException>> | Exception |
Class <<CORBA Typedef>> | Typedef, array, sequence |
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 Navigator view and in the Package Explorer view of the Java perspective.
You can use the mapping feature to specify alternate names for files that the transformation generates without modifying the source model. Except for components, you can only rename UML elements with simple identifiers. You can rename UML components with either a simple identifier or with a valid partial path that is relative to the target container in which the IDL file is generated. The path should end with the name of the IDL file. For example, if you rename ComponentA as dirA\A, the transformation generates A.idl in the directory named dirA, instead of in the top level of the target container.