Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > IDL Code > Mapping information > Summary of Mappings for IDL code (IDL code) > Bound module mapping for IDL (IDL code)
  
Bound module mapping for IDL (IDL code)
For each Bound Module, ACS generates an IDL file. ACS generates code similar to this:
//==========================================
/// @file Package1_Message1_conn.idl
//==========================================
#ifndef PACKAGE1_MESSAGE1_CONN_IDL
#define PACKAGE1_MESSAGE1_CONN_IDL
#include <Components.idl>
#include <ccm_dds.idl>
#include "Package1_Message1_msg.idl"
#pragma ciao lem "Package1_Message1_connE.idl"
module Package1
{
\u00a0\u00a0\u00a0typedef sequence<Message1_msg> Message1_msgSeq;
\u00a0\u00a0\u00a0module CCM_DDS::Typed<Message1_msg, Message1_msgSeq> Message1_conn;
};
#endif
ACS uses Bound Modules for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
The generation of a Bound Module in an IDL file is derived from the properties of the Bound Module.
Child items:
None.
Properties:
• If the Description property has a value, ACS generates the Description as a comment at the beginning of the IDL file.
• ACS generates the Name property as the name of the IDL file.
Note ACS may modify the file name to make it valid for IDL. You can specify the exact file name to use through the CODE_GENERATION_NAME property of a Bound Module. Other properties are ignored.
Tag Definitions:
msg - the Message that is associated with the Bound Module, that is, the Message that is used as the argument for T.
Note that when a Structure is used to instantiate a Bound Module, the IDL Profile changes that Structure to a Message.