public class WaterMeterIoV3 extends Schema<WaterMeterIo,WaterMeterIoV3>
Schema.Meta| Modifier and Type | Field and Description |
|---|---|
int |
nodeidx |
WaterMeterIo.IoStatsEntry[] |
persist_stats |
__meta, _impl_class, _version_pattern| Constructor and Description |
|---|
WaterMeterIoV3() |
| Modifier and Type | Method and Description |
|---|---|
WaterMeterIo |
createImpl()
Create an implementation object and any child objects but DO NOT fill them.
|
WaterMeterIoV3 |
fillFromImpl(WaterMeterIo i)
Version and Schema-specific filling from the implementation object.
|
acceptsFrame, createAndFillImpl, extractVersion, fillFromParms, fillImpl, getExperimentalVersion, getHighestSupportedVersion, getImplClass, getImplClass, getLatestVersion, getSchemaVersion, markdown, markdown, markdown, markdown, newInstance, register, registerAllSchemasIfNecessary, schema, schema, schema, schema, schema, schemaClass, schemaClass, schemaClass, schemaClass, schemasclone, frozenType, read_impl, read, readExternal, readJSON_impl, readJSON, toJsonString, write_impl, write, writeExternal, writeHTML_impl, writeHTML, writeJSON_impl, writeJSON@API(help="array of IO info", direction=OUTPUT) public WaterMeterIo.IoStatsEntry[] persist_stats
public WaterMeterIo createImpl()
SchemaFor objects without children this method does all the required work. For objects with children the subclass will need to override, e.g. by calling super.createImpl() and then calling createImpl() on its children.
Note that impl objects for schemas which override this method don't need to have a default constructor (e.g., a Keyed object constructor can still create and set the Key), but they must not fill any fields which can be filled later from the schema.
TODO: We *could* handle the common case of children with the same field names here by finding all of our fields that are themselves Schemas.
createImpl in class Schema<WaterMeterIo,WaterMeterIoV3>public WaterMeterIoV3 fillFromImpl(WaterMeterIo i)
SchemafillFromImpl in class Schema<WaterMeterIo,WaterMeterIoV3>