org.knime.core.data
Interface DataValue

All Known Subinterfaces:

BitVectorValue, BitVectorValue, BooleanValue, BoundedValue, ByteVectorValue, CollectionDataValue, ComplexNumberValue, DateAndTimeValue, DoubleValue, FuzzyIntervalValue, FuzzyNumberValue, ImageValue, IntervalValue, IntValue, ListDataValue, LongValue, NominalValue, PMMLValue, PNGImageValue, PortObjectValue, SetDataValue, SparseListDataValue, StringValue, TimestampValue, XMLValue

All Known Implementing Classes:

BitVectorCell, BlobDataCell, BlobWrapperDataCell, BooleanCell, ComplexNumberCell, DataCell, DateAndTimeCell, DenseBitVectorCell, DenseByteVectorCell, DoubleCell, FuzzyIntervalCell, FuzzyNumberCell, InputDataRow.WildCardCell, IntCell, IntervalCell, ListCell, LongCell, PMMLBlobCell, PMMLCell, PMMLCellContent, PNGImageBlobCell, PNGImageCell, PortObjectCell, SetCell, SotaDoubleCell, SotaFuzzyCell, SparseBitVectorCell, SparseByteVectorCell, SparseListCell, StringCell, TimestampCell, XMLBlobCell, XMLCell, XMLCellContent

public interface DataValue

The interface all value interfaces of DataCells are derived from. DataCells implement different DataValue interfaces to allow access to generic (or complex) fields from the cell. Typically a DataValue brings along its own (set of) renderers, an icon (which is displayed in table column headers, for instance) and a comparator, which are all defined through the definition of a static member UTILITY.

For more information regarding the definition of new DataCells see the package description and the manual on how to define new types, in particular the remarks on DataValue.

Author:

Bernd Wiswedel, University of Konstanz

Nested Class Summary

static class

DataValue.UtilityFactory Implementation of the meta information to a DataValue.

Field Summary

static DataValue.UtilityFactory

UTILITY Static singleton for meta description.

Field Detail

UTILITY

static final DataValue.UtilityFactory UTILITY

Static singleton for meta description. This field is accessed via reflection in the DataType class. It is used to determine renderer, comparator, and icon. Sub-Interfaces will "override" this static member, if they desire to define own renderers, comparator, and/or icon.