Client mapping for IDL (IDL code)
For each Client, ACS generates a uses or uses multiple declaration in the appropriate IDL file. ACS generates code similar to this:
// Client declarations
uses Interface1 Client1;
uses Interface1 Client1;
ACS uses Clients for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
The generation of a Client in an IDL file is derived from its Properties.
Child items:None.
Properties:• If the Description property has a value, ACS generates the Description as a comment on the line before the uses or uses multiple declaration.
• ACS generates the Name property as the name of the client in the code.
Note ACS may modify the client name that is added to the code to make it valid for IDL. You can specify the exact client name to add to the code through the CODE_GENERATION_NAME property of a Client. Tell me more...
Other properties are ignored.
Tag Definitions:The following Tag Definitions are applied to a Client by the «Client» stereotype:
• If the tagged value of the isMultiple tag definition is set to FALSE, ACS generates a uses declaration.
If the tagged value of the isMultiple tag definition is set to TRUE, ACS generates a uses multiple declaration.
• If the tagged value of the Asynchronoustag definition is set to TRUE, ACS generates pragmas similar to the following for the Client:
In the IDL file generated for the Component:
#pragma ciao ami4ccm receptacle "Component1::Interface1"
In the IDL file generated for the Interface:
#pragma ciao ami4ccm interface "Interface1"
#pragma ciao lem "Interface1AE.idl"
#pragma ciao ami4ccm idl "Interface1A.idl"
#pragma ciao lem "Interface1AE.idl"
#pragma ciao ami4ccm idl "Interface1A.idl"