The Application Tree lists generated elements in the open model selected in the editor area.
You can use the Application Tree in the model editor to navigate to and access a generated element. With an open model having focus in the model editor, click the Application Tree
tab to expose the panel and view the WebApp folder and subfolders in which generated elements are listed by type. If the Application Tree
tab is not visible, click the arrow icon on the left side of the editor area to shrink the selected panel and expose the Application Tree panel.
The generated elements for a model are displayed in tree form under the WebApp folder. Folders representing element types can be expanded and collapsed. For example, all variables in the WebApp are contained in the Variable folder. The same is true for other types of elements. This organization of generated elements allows you to easily visualize what the WebApp contains and how the WebApp changes during regeneration. For example, you can use the Application Tree to determine what a builder adds to the WebApp.
Click the companion Pages
tab to more readily access page and form elements.
For each type of generated element that is selected in the Application Tree, the corresponding code is displayed in the Source panel.
Use the Source panel to examine the related code generated by a builder call or a method.
If you expand a folder in the Application Tree and click on a WebApp object, the builder responsible for creating the object is highlighted in the builder call list. Likewise, if you select a builder call in the Outline view and enable Link with WebApp Tree
, the generated elements associated with that builder call are selected in the Application Tree.
The Application Tree operation is closely coupled with the Source view and the Design view.
Controls in the Application Tree
A standard Eclipse tree filter is available at the top of the Application Tree. If you type text in the filter, an incremental search is performed. Only those resources that have the filter characters at the start of their names are displayed under the WebApp
folder in their related sub-folders. If you type the asterisk character (*
) first and text, those resources that have the text anywhere in their names are displayed. An icon is available to clear the filter and display all resources.
The Application Tree supports a popup menu that you can use to more readily open builders that created or can modify the selected element.
If you set Show Hidden Object
in IBM® WebSphere® Portlet Factory Designer preferences, you can see additional objects under the WebApp
Typical folders in the Application Tree
Typically, you can see the following folders in the Application Tree.
Displays Comment builder calls. These calls are used to document model construction or segments of builders in the builder call list. They provide a handy means for documenting a model.Data Services
Displays information about generated elements used to access IBM WebSphere Portlet Factory Data Service Layer. This common layer is used to access the back end or external data, and makes it possible to separate the user interface (UI) from the data. For example, this layer allows you to have one model that is used to access data and a linked model that provides the business logic or user interface for accessing the data. Objects that might be displayed as Data Services include: Service Calls, SQL Calls, and data access requests made by various View and Form builders.Events
Linked Java Objects
Displays event handler information. (The Event Declaration itself is not displayed.) When an Error Handler builder call is added to a model, its information is displayed in the Source panel. Each event in the WebApp is listed in the Event tree. User defined events (created with an Event Declaration builder) are prefixed with User
and displayed only when there is an Event Handler builder present that handles the event. Event Declarations add two methods to the WebApp. These methods show up under the methods folder. The following is a typical event viewer display:
Displays information about each LJO in the model, including status (persisted for failover) and the public methods within the LJO.Methods
Displays highlighted Java code of selected method. The viewer displays the entire generated methods class, and the selected method is highlighted.Pages
Displays information about each page in the WebApp. The upper panel describes page name status (public) and properties. The lower panel displays page HTML and JSP code and tags. Click on a node (page control) listed under an individual page to jump to the code that implements that node.Properties
Use the Pages panel for more direct access to pages and forms in the model.
Displays information about properties that apply to the overall WebApp. Various builders (for example, the Schema builder) create and use WebApp properties. Schemas
Displays the XSD and XML markup defining a schema and the generic structure of elements and attributes (not actual schema data). The upper panel displays schema source and caching information. The lower panel displays schema XSD elements and references.Variables
Displays information about each variable in the WebApp, whether the variable was created manually or automatically by a builder. The upper panel presents information about variable name, status, type, and persistence and properties. For object types, the class name and instantiate method is also listed.
Parent topic: About the model editor