Dependency mapping for IDL (IDL code)
For each Dependency that links an item from which an IDL file is generated to another item from which an IDL file is generated, ACS generates a file include directive in the IDL file that is generated for the dependent item. ACS generates code similar to this:
#include "Package1_Component2.idl"
ACS generates IDL files for Bound Modules, Components (that do not own Component Parts), Interfaces, Messages and Packages.
You can prevent ACS from generating a file include directive for a Dependency through the «IDLDependency» stereotype.
Note that for Packages and Components, file include directive text can also be defined through the Includes tag definition, which can be applied to items from which IDL files can be generated through the «Source» stereotype from the IDL Profile.
The generation of a Dependency in an IDL file is derived from the source and destination items it links, and the tagged value set for the ignore Tag Definition applied by the «IDLDependency» stereotype.
You can apply the «CORBASupports» stereotype to an interface realization Dependency, however this stereotype does not affect how ACS generates the Dependency.
Child items:Not applicable.
Properties:• If an IDL file is generated for the source item (dependent item) and an IDL file is generated for the destination item (dependee item); in the IDL file that is generated for the source item, ACS generates a #include statement that references the IDL file that is generated for the destination item.
Other properties are ignored.
Tag Definitions:The following Tag Definitions are applied to a Dependency by the «IDLDependency» stereotype:
• If the tagged value of the ignore tag definition is set to FALSE, ACS does not generate any file include directives for the Dependency.