Developer Tools
JDeveloper
When you complete the steps for creating a detail table in ADF Swing Panel, the panel in the Java visual editor should look similar to this:
In the Structure window, you should see the UI component hierarchy:
In the Application Navigator, the View project should look like this when fully expanded:
The files generated by the Create ADF Swing Empty Panel dialog are:
In the Application Navigator, double-click DataBindings.cpx and OrderItemsPanelPageDef.xml to open each file in the overview editor. If necessary, click Overview in the editor window to view the file in the overview editor.
In
DataBindings.cpx, notice that JDeveloper has added a third page definition file entry:
view_OrderItemsPanelPageDef, representing the detail panel page definition file.
The first time you dropped the detail collection
OrderItemsView2 on the panel in the visual editor, JDeveloper added the iterator binding
OrderItemsView2Iterator to the detail panel page definition
OrderItemsPanelPageDef.xml. The iterator binding references an iterator for the detail collection, which facilitates iterating over its data objects. The iterator binding also manages currency and state for the data objects in the collection.
Click Source to see the XML source code in OrderItemsPanelPageDef.xml.
The number of data objects that the table control will display is determined by the iterator binding's RangeSize value. Because the RangeSize iterator value is a declarative property of the page definition, the UI designer can easily change it to specify the number of data objects to fetch from the business service. By default, the iterator binding will fetch and display 25 data objects at a time.
<executables>
<iterator id="OrderItemsView2Iterator" RangeSize="25"
Binds="OrderItemsView2" DataControl="AppModuleDataControl"/>
</executables>
When you dropped the table control on the detail panel, JDeveloper added the
OrderItemsView2 ADF binding object to the page definition file. The table binding object references the iterator binding, which in turn references the iterator for the data collection. In the table binding, the
AttrNames element contains a a child element for each attribute that you want to be available for display or reference in each row of the table.
<bindings>
<table ColumnSort="entireCollection" IterBinding="OrderItemsView2Iterator"
id="OrderItemsView2" xmlns="http://xmlns.oracle.com/adfm/jcuimodel">
<AttrNames xmlns="http://xmlns.oracle.com/adfm/uimodel">
<Item Value="OrderId"/>
<Item Value="LineItemId"/>
<Item Value="ProductId"/>
<Item Value="Quantity"/>
<Item Value="UnitPrice"/>
...
</AttrNames>
</table>
</bindings>
Copyright © 1997, 2009, Oracle. All rights reserved.