extended port (publisher) mapping for IDL (IDL code)
For each Extended Port (Publisher), ACS generates a port declaration in the IDL file that is generated for the owning Component. ACS generates code similar to this:
// Extended Publisher declarations port Package1::Message1 _conn::DDS_Write MyExternalPortPublisher;
ACS uses Extended Port (Publisher) items for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
Note that if the owning Component is an assembly (it owns Component Parts), no IDL file is generated for that Component.
The generation of an Extended Port (Publisher) in an IDL file is derived from its Properties.
Child items:
Not applicable.
Properties:
• ACS generates the Data Type property as the type of the port. In the preceding example, the data type is DDS_Write.
• If the Description property has a value, ACS generates the Description as a comment on the line before the port declaration.
• ACS generates the Name property as the name of the port.
ACS may modify the port name that is added to the code to make it valid for IDL. You can specify the exact port name to add to the code through the CODE_GENERATION_NAME property of an Extended Port (Publisher).
Tell me more...
Other properties are ignored.
Tag Definitions:
• boundModule - ACS uses the name of the Bound Module (and the Port Type) to declare the port.
• msg - ACS uses the message property when generating code for an Extended Port (Publisher).
Child items:
Properties:
Tag Definitions: