The role of the browse page is to allow the user to view and navigate the data objects, one at a time. You will add databound components to the
br-o.jspx page to create a read-only form and table. Both the read-only form and read-only table supply the master/detail functionality in this browse page. At runtime, the orders are shown one at a time, with the order information in the read-only form, and the order's line items in the read-only table.
To begin designing the browse page, use the JDeveloper data binding tool, known as the Data Controls panel. The Data Controls panel is part of the Application Navigator where Oracle ADF data controls are represented. The data controls can be added to a page as UI controls. Examples of UI controls include input fields, forms, and tables. To access the data controls, expand the Data Controls panel, then expand the application module node FODModuleDataControl to show the structure of the business service.
When you drag a node from the Data Controls panel to the page, the Create context menu displays, which you will use to first create a form and then a table.
For navigating through orders in the form, you will add a series of buttons to the browse page.
In a previous cue card when you created the page flow diagram, you defined the navigation outcome
goEdit from the browse page to the edit page. On the browse page, to enable users to navigate to the edit page, you will add a command button and set the button's
action property to the
goEdit outcome. At runtime when users execute the command button, the application navigates to the edit page where they can then edit the complete details of the order that is currently displayed on the form in the browse page.
Copyright © 1997, 2009, Oracle. All rights reserved.