Structure of Tables

The main class of the Java-client Table Bean is the Table class, which is defined in the oracle.dss.table package. The Table class extends the oracle.dss.gridView.GridView class, as does the Crosstab class. The GridView class extends oracle.dss.dataView.Dataview. The Dataview class implements the DataviewCommon interface.

The main class of the HTML-client Table Bean is the ThinTable class, which is defined in the oracle.dss.thin.beans.table package, The ThinTable class extends oracle.dss.thin.beans.gridView.ThinGridView class, as does the ThinCrosstab class. The ThinGridView class extends oracle.dss.thin.beans.dataView.ThinDataview. The ThinDataView class implements the ThinDataViewCommon interface. The ThinDataViewCommon interface extends the DataviewCommon interface.

Both the Java-client table and the thin table have PagingControl components, which allow users to view different logical pages of data. The paging controls are implemented differently for the Java-client table and the thin table, but in both cases, you call getPagingControl to get the paging control.

The following diagram illustrates these relationships.

Class structure for tables; described in text

Header and Databody components

Both the thin table and the Java-client table have header components that describe the data in the table. The column header component class is ColHeader, and the row header component is the RowHeader. Both classes extend TableHeader. All three of these classes are defined in oracle.dss.table. In both the Table class and the ThinTable class, you call getColumnHeader to retrieve the column header, and you call getRowHeader to retrieve the row header for the table. Both getColumnHeader and getRowHeader return a GridViewHeader. The TableHeader implements the GridViewHeader interface, so you can call any GridViewHeader method to set properties of the headers in a thin table or in a Java-client table.

The following diagram illustrates the relationships between these classes and the GridViewHeader interface.

Class structure for table headers; described in text

As with the headers, both the Java-client table and the HTML-client table have a databody component. The TableDatabody class, which is defined in the oracle.dss.table package, is the databody class for both the Crosstab and the ThinCrosstab. You call getDatabody to retrieve the databody. The getDatabody method returns a GridViewDatabody, which the TableDatabody implements. You can call methods of the GridViewDatabody to change the appearance of the databody.

The following diagram illustrates that the TableDatabody class implements the GridViewDatabody interface.

Table databody class structure; described in text