The object is used by using a FeatureCollection. In this case the control hangs on to a reference to the FeatureCollection and populates the table entries directory from it. This method results in a single page containing all features.
If the FeatureCollection implements the {@link IAdaptable} interface and adapts to{@link ICellModifier} then the table is editable. The {@link ICellModifier} is used to modify thefeatures. The Column properties passed to the {@link ICellModifier} are the attribute name of theattribute being modified.
If the FeatureCollection implements the {@link IAdaptable} interface and adapts to{@link CellEditor[]} then the cell editors will be used to edit the cells. This is optional forediting. By default a {@link TextCellEditor} is used for editing most cells, and an{@link AttributeValidator} is used to validate the new values. The first column is for the fidcolumn and will not be used since FIDS are assigned by the datastore and can not be modified. The number of Items the array (this is the same for the cell editor validators and cell editor listeners) must be either the number of attributes in the feature type or the number of attributes + 1 (one for the FID column). If the number of editors it Attributes+1 then the first element in the array will not be used as it is assumed to be a placeholder for the fid column.
If the FeatureCollection implements the {@link IAdaptable} interface and adapts to{@link ICellEditorValidator[]} then the validators will be used to validate the cells.
If the FeatureCollection implements the {@link IAdaptable} interface and adapts to{@link ICellEditorListener[]} then the listeners will be added to the {@link CellEditor}s.
@author jdeolive @author jeichar @since 0.3 | |