Class mapping for IDL (IDL code)
For each Class, ACS generates a struct in the appropriate IDL file. ACS generates code similar to this:
struct Class1
{
...
};
//@top-level false
ACS generates a Class as a Union when the «CORBAUnion» stereotype is applied to it. For more information about how Unions are generated, see Union mapping for IDL (IDL code).
The generation of a Class in an IDL file is derived from the items it owns, properties of the Class, and the tagged values set for Tag Definitions applied by the «Source» stereotypes from the IDL Profile.
A Class can also be used for modeling module scoped constants. Tell me more...
Child items:
If the Class owns Attributes, ACS generates attribute declarations. For Attribute mapping information, see Attribute mapping for IDL (IDL code).
Reverser Notes: When reverse engineering a struct's attributes, the Reverser will reverse engineer the attribute as a Role if all of the following statements are true:
The IDL attribute's data type can be identified as a struct or interface in the code being reverse engineered.
The struct or interface that is used as a data type is being reverse engineered.
The Reverser cannot match the IDL attribute to an Attribute in the Model.
If the Class owns Roles, ACS generates an attribute declaration. For Role mapping information, see Role mapping for IDL (IDL code).
Other child items are ignored.
Properties:
If the Description property has a value, ACS generates the Description as a comment on the line before the struct declaration.
ACS generates the Name property as the name of the struct.
Note ACS may modify the struct name that is added to the code to make it valid for IDL. You can specify the exact struct name to add to the code through the CODE_GENERATION_NAME property of a Class.
If the Union property is set to TRUE (Union check box selected on Property Pages) and the «Union» stereotype is applied to the Class, ACS generates the Class as a union. For Union mapping information, see Union mapping for IDL (IDL code).
Other properties are ignored.
Tag Definitions:
The «Source» stereotype applies the following Tag Definitions.
If the tagged value of the ignore tag definition is set to FALSE, ACS does not generate the Class.
The other Tag Definitions that are applied by the «Source» stereotype are ignored when generating a Class.
Was this helpful?