The Action List builder adds a set of one or more actions to the WebApp.
When you call the ActionList, each action in the set executes before returning control back to the web application. You can easily profile the entire list of actions, or profile one or more individual actions within the list. Each action in the list can do one of the following:
- Display a page.
- Execute a method.
- Compare the values of two variables.
- Return the value of a variable, the result of a method call, the result of a Java Expression, or an Input value.
- Execute an action based on conditional logic.
- Add a comment to the action list.
Note: This does not get executed, but acts as a comment for the ActionList and is analogous to a comment embedded in a Java code segment.
Assign or append values to variables
Select the Assignment element displayed in the Action Chooser and use the reference chooser to select the element in the model that will supply the value. Then select the variable in which to store the value in the displayed dialog.Return a value from an Action List
Select the Return element displayed in the Action Chooser and use the reference chooser to select an element in the model whose value you want to return.Return of the Last Action
The action list automatically returns the results of the last action. You do not need to explicitly return the result of that action.Drag and drop actions in the list
You can rearrange the actions in the action list by dragging and dropping them into the desired order.Insert and Delete actions in the list
You can insert and delete actions by right-clicking and choosing the appropriate operation from the pop-up menu.Logging systemOut Messages
This builder sends systemOut messages to the debugTracing log located in the published .../WEB-INF/logs directory. You can disable all SystemOut actions across all Action Lists in all models in a WAR
For example, in IBM® WebSphere® Portal server, the log files for running as a portlet are found in the directory of the published portlet WAR file. If the portlet is run standalone or the widget is run locally, log files can be found in the published enterprise application directory.
Note: You can disable all SystemOut actions across all Action Lists in all models in a WAR by setting log4j.logger.bowstreet.system.out=WARN in the log4j.properties of a production WAR. When logging is disabled, the webApp methods generated for Action Lists do not create log strings. The benefit of this is that you will be able to leave your logging / trace statements in-place for production, without experiencing a performance degradation.
Parent topic: Builder help
About using the builder call editor
Web Service Enable builder