Model Container builder inputs - Portlet Factory v6.1.2

Portlet Factory, Version 6.1.2

Model Container builder inputs

This topic describes the inputs for the Model Container builder.

Table 1. Model Container builder inputs
Input name Description
Name Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Page Location Page or pages on which this builder call acts.
Model Enter the name of the model you want to place in the container. The builder looks in the WEB-INF/models directory.
Profile Name the profile to use when the model container dynamically links in a model. The profile name can also be stored in a variable.
Model Initialization data Enter data you want to be accessible to the model when it is loaded into the container. This data can be the following:

Linked Java Object
Method
Model
Text
Variable

Model to Load on Error Enter the name of the model to load when there is an error.
ID for this Instance Type a unique identification (ID) for the models in the repeated region. The unique identifier is usually an indirect run-time reference, such as Model${Variables/LoopCount}, to each model. Each successive iteration through the repeated region produces a unique ID, for example, Model1, Model2.
Advanced

Inherit Explicit Profile Enable this input if you want the profiled builder call inputs in the linked model to get their values from the profile passed explicitly as part of the request for the host model.
The normal profile selection for the model does not take place if you choose to inherit explicit profiles. All profiled inputs get their values from the profile passed to the host model.
Instance Rule Determines whether the contained model instance is to be accessed using a linked model path from the topmost container model instance (Keep separate model data for each model container within a portlet session) or stored directly in the (portlet) session (Allow model data to be shared across model containers within a portlet session (session singleton)).
Select one of the following:

Keep separate model data for each model container within a portlet session

Allows multiple instances of the linked model to be generated for requests in the same session. Always use this option unless you know that you need the other setting and are sure that it will not break anything.

Allow model data to be shared across model containers within a portlet session (session singleton)

Have only one instance of this model generated for all the requests in a session.

Request Events

Forward Request Events By default, OnRequest and OnRequestComplete events are delivered to the top-level model in a request. Check this box to send the events to the contained model as well.

Parent topic: Model Container builder

Library | Support |

Input name	Description
Name	Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Page Location	Page or pages on which this builder call acts.
Model	Enter the name of the model you want to place in the container. The builder looks in the WEB-INF/models directory.
Profile	Name the profile to use when the model container dynamically links in a model. The profile name can also be stored in a variable.
Model Initialization data	Enter data you want to be accessible to the model when it is loaded into the container. This data can be the following: Linked Java Object Method Model Text Variable
Model to Load on Error	Enter the name of the model to load when there is an error.
ID for this Instance	Type a unique identification (ID) for the models in the repeated region. The unique identifier is usually an indirect run-time reference, such as Model${Variables/LoopCount}, to each model. Each successive iteration through the repeated region produces a unique ID, for example, Model1, Model2.
Advanced
Inherit Explicit Profile	Enable this input if you want the profiled builder call inputs in the linked model to get their values from the profile passed explicitly as part of the request for the host model. The normal profile selection for the model does not take place if you choose to inherit explicit profiles. All profiled inputs get their values from the profile passed to the host model.
Instance Rule	Determines whether the contained model instance is to be accessed using a linked model path from the topmost container model instance (Keep separate model data for each model container within a portlet session) or stored directly in the (portlet) session (Allow model data to be shared across model containers within a portlet session (session singleton)). Select one of the following: Keep separate model data for each model container within a portlet session Allows multiple instances of the linked model to be generated for requests in the same session. Always use this option unless you know that you need the other setting and are sure that it will not break anything. Allow model data to be shared across model containers within a portlet session (session singleton) Have only one instance of this model generated for all the requests in a session.
Request Events
Forward Request Events	By default, OnRequest and OnRequestComplete events are delivered to the top-level model in a request. Check this box to send the events to the contained model as well.