See Also
The
Outline window
provides you with a hierarchical view of the objects
in your application, both visible objects, such as components, and invisible
objects, such as RowSets. To open the Outline window, choose
View > Outline.
In this window, you see a section for the current page in the application
plus all the non-page managed beans, such as any session beans, application beans,
or request beans. If you click a section
heading, you see its contents. The Outline window
changes focus based on the bean you are working on. For example,
if you are working on Page1 in the Visual Designer, the
Outline window opens the Page1 Section and highlights the component
you have selected. The following list describes each type of
section:
- page-name Section. The page-name section shows all the
objects on the current page, including nonvisual objects like database table
RowSets. The runtime scope of each page is Request, meaning that information is
not saved between page requests.
- The beans sections. You can add properties, interfaces, and classes to a bean
by selecting it and right-clicking. You can also view the code for a bean in the
Java Editor by right-clicking the bean and choosing Open.
- RequestBean Section. This bean has a runtime scope of Request. A request is a single transmission of an HTTP request from the client to the server plus the corresponding response, which can be another page. In most cases, the request begins with the clicking of a button or a link and ends with the response of an HTML page to be displayed. Use this bean to store information that you need to preserve for only a single user request, such as information to pass to the next page. Any value that you store in the Request Bean disappears as soon as the request ends.
- SessionBean Section. By default, there is one session
bean for each project. This bean has a runtime scope of Session. Use this
bean to store information that you want to preserve
across page requests for a single user session, such as a user's logon information.
- ApplicationBean Section. By default, there is one
application bean for each project. This bean has a runtime
scope of Application and is where you store information that
you want to preserve across all user sessions, such as the contents of
a drop-down list showing a list of all countries.
Using the Outline Window
You can use this window as follows:
- You can drop components directly from the Palette or Servers window on
components in the Outline window to determine the parent object. You can drop between components (when there are multiple
siblings) to control where in the list a child appears,
such as for the children of a grid panel.
- You can reorder, and reparent, components by dragging them around within
the outline. For example you can drag a button from the form into a grid panel
component for example, or back out.
- You can use
the Outline window to work with elements of a page that
are hard to select in the Visual Designer because they
are not visual, embedded in other components or simply referenced
by those components. For example, the checkbox list is composed of several other
components. If you select the checkboxList#SelectItems component in the
Outline window you can bind it to a bean property or database that will provide
the options displayed in the component. For more information,
see Checkbox
List Component. There is also a tutorial that describes
how to set up binding for a similar list component, Using Listbox
Components, which is on the web at
Java Studio Creator Tutorials
- Select a component's node and edit its properties.
- Right-click a component's node and work with the same contextual
menu choices as you would in the Visual Designer.
- You can select a form component in the Outline window
and delete it. However, be sure not to delete the original
form created for the page. Every page must have at least one
form in it.
- See Also
- About Projects
- About the Visual Designer
- Application Bean Node
- Request Bean Node
- Session Bean Node