Operation mapping for IDL (IDL code)
For each Interface and Value Type scoped Operation, ACS generates an Operation declaration in the IDL file created for the Interface. ACS generates code similar to this:
// Operation declarations
char Operation1();
ACS uses Operations for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
The generation of an Operation in an IDL file is derived from its child items and its properties.
Child items:
Properties:
• If the Description property has a value, ACS generates the Description as a comment on the line before the operation declaration.
• ACS generates the Name property as the name of the operation in the code.
| ACS may modify the operation name that is added to the code to make it valid for IDL. You can specify the exact operation name to add to the code through the CODE_GENERATION_NAME property of an Operation.
Tell me more... |
• If the Return Type property is set, ACS generates the value as the operation's return type.
If no data type is specified, ACS generates void by default, except for constructors in which case no return type is generated. If you want ACS to generate a different default in the absence of a data type for an Operation, change the default value that is specified in the IDL_Sync.ini file.
Tell me more...Reverser Notes : When reverse engineering a method's return type:
◦ If the return type is modeled in the Model or is going to be reverse engineered to the Model, the Operation's Return Type references the appropriate item.
◦ If the return type is not modeled in the Model and is not going to be reverse engineered to the Model, the Operation's Data Type is set to the name of the return type as text.
Other properties are ignored.
Tag Definitions:
• If the «CORBAValueFactory» stereotype is applied to the Operation, ACS generates the Operation as a factory operation.