The builder call list contains all the builder calls that define your model.
The builder call list is rendered in the Outline view of your development environment when a model is opened for editing. The builder call list displays the sequence number, name, and type of each builder call in the model, and indicates whether or not the builder call is profiled.
You can use the builder call list to sort, filter and categorize builder calls. You can manage a builder call in the list by selecting it and using the commands (cut, copy, paste, and so on) available in the context (right-click) menu.
Disabled builder calls are greyed-out.
IBM® WebSphere® Portlet Factory executes these builder calls in the numeric order in which they appear in the builder call list. As each builder call executes, it adds elements to, or modifies elements in, the WebApp object.
When you generate the web application from the model, WebSphere Portlet Factory resolves any indirect references you have used for builder call inputs and supplies any profiled builder call inputs with values from the appropriate profile.
As a result of the linear execution of builder calls, the order in which you place builder calls in the list is important. For example, to reference the value returned by a method in a builder call input, add that method to the WebApp prior to the current builder call.
As you develop your model, you may add a builder call that cannot access the objects that it needs. For example, if you add or move a Data Field Modifier builder call before the Data Page builder call on whose elements it operates, the WebSphere Portlet Factory Designer displays a warning similar to the following:
Field selector " [page1]ShowEmployeeData/RowSet/Row/EMPNO" did not evaluate to any fields.
Ensure that this BuilderCall follows the corresponding Data Page BuilderCall.
In this case, once you drag the Data Field Modifier builder call below the Data Page builder call, the error is eliminated.
In general, as you add builder calls to the builder call list, be aware of the dependencies one call has on another. Make sure that you do not place a call in the list that depends on a call (or call artifact) that is yet to be created. Populate the builder call list in a top down manner and make sure that any call you add to the list depends only on the builder calls above it.
Regardless of how the builder call list is sorted (for example, alphabetically by name or by type), builder execution is based on the numeric order of builder calls within the builder call list.
Parent topic: About the Outline view