The builder call editor allows you to specify all the input values to a builder call.
You can also reference elements in an XML structure and locate control builder calls on one or more pages in the model.
The following builder call input groups are common to many builders:
Expanding the Properties input group displays the following inputs that describe information about the builder call:
The Enable Builder value, True or False, marks the builder call to be included in generation or not. The default value is True. You can profile this input to enable or disable a builder call for a particular profile.Category
This input is no longer used. Comment
Enter a comment that describes some relevant information about how you are using this builder call. When you open the builder call, these comments are displayed in the properties section of the builder call editor.
Adding Eclipse tasks to model
You can add Eclipse tasks to models using the comment field. You create tasks by adding comments to any builder. Use these tasks to indicate that there is work TODO or FIXME items to be completed. TODO's are normal priority tasks and FIXME's are high priority tasks. Each builder can have multiple tasks. When you complete the task you can remove the comment which will remove the task from the model.
Indicate each task with a TODO or FIXME at the beginning of the line in upper case. For example:
TODO Update the style for this page
FIXME Add SmartPhone support
Builders can also have tasks added when they are called through the API. When a builder calls a target builder, the calling builder adds to the call a message with the severity indicator task. The indicated message is added to the target builder.
The message can have any text that the builder wants; but if they want the standard TODO and FIXME behavior, the message needs to start with TODO or FIXME. These tasks are displayed until the builder no longer generates these messages. This will allow builders to dynamically add tasks to assist users in advanced functionality.
Expanding the Arguments group displays the following inputs that allow you to pass arguments to the specified action:
Enter the name of the argument for the specified action.Value
Enter the value for the argument. You can use the reference chooser to select a value from one of the elements in the web application.
Expanding the Advanced group displays additional inputs that you can set to fine tune the builder behavior according to your requirements.HTML Attributes
Expanding the HTML Attributes
group displays the following inputs that describe how control builder calls (such as Button or Text Input) should be rendered in HTML.
If the page on which this control uses a cascading style sheet (CSS), enter the style class name to apply to this control.Style
Enter HTML style syntax for the control that the builder adds to the page.
Other options might be present, depending on the builder.
About specifying input values
Most inputs to a builder call can take a value derived from an indirect reference, a Java expression, or directly from a String value. Some inputs that require a name to a specific object like a variable or model use specific choosers that filter out inappropriate elements.
Parent topic: The IBM WebSphere Portlet Factory interface
Choosing builders for common tasks