Action Processor Editor Editor Tab
Use the Editor tab to define the properties and generate the code for an action processor.
Field | Use |
---|---|
Description |
Specify a description for the Action Processor editor. |
Vendor, Technology, and Software Load |
Displays the vendor, technology, and software version for the action processor entity in the cartridge project. |
Action |
Select an action from the list of actions or enter an action not in the list. |
Type |
Select the type of action processor:
|
Class and Method |
The Java Action Processor (with Code Generation) and the CLI Code Generation options display the class and method names mapped to the action processor after the code is generated by clicking the New button. Java Action Processor displays the default values of myProcessor and execute respectively. The code for the default values does not exist. You must change these values to existing class and method names and map them using Select. |
State Table and Program |
Displays the default values of S_MY_STATE_TABLE and doAction respectively. Note: The code for the default values does not exist. You must change values to existing state table and program names and map them using Select. |
Open |
Click to see the code. This button is enabled only when the code is available. |
New |
Click to create the action processor implementation. Note: Enabled only for Java Action Processor (with Code Generation) and CLI Code Generation action processors. |
Select |
Select Java implementation or state table implementation. Use this button to map the class and method to the Java Action Processor or to map the state table and program to the State Table action processor. Note: Enabled only for Java Action Processor and State Table action processors. |
Command Overview |
Enter documentation in the Command Overview area for the MML commands. |
Output |
Enter comments in the output area from the action processor (for example, return the following parameters as INFO or CSDL) in the Output area. |
Development Notes |
Enter comments provided by the cartridge developer in the Development Notes area. |