public class WaterMeterIoV3 extends RequestSchemaV3<WaterMeterIo,WaterMeterIoV3>
SchemaV3.Meta
Schema.AutoParseable
Modifier and Type | Field and Description |
---|---|
int |
nodeidx |
WaterMeterIo.IoStatsEntry[] |
persist_stats |
_exclude_fields
Constructor and Description |
---|
WaterMeterIoV3() |
Modifier and Type | Method and Description |
---|---|
WaterMeterIo |
createImpl()
Create an appropriate implementation object and any child objects but does not fill them.
|
WaterMeterIoV3 |
fillFromImpl(WaterMeterIo i)
Fill this Schema from the given implementation object.
|
createAndFillImpl, extractVersionFromSchemaName, fillFromBody, fillFromImpl, fillFromImpl, fillFromParms, fillFromParms, fillImpl, fillImpl, getImplClass, getImplClass, getSchemaName, getSchemaType, getSchemaVersion, init_meta, markdown, markdown, newInstance, newInstance, setField, setSchemaType_doNotCall
asBytes, clone, copyOver, frozenType, read, readExternal, readJSON, reloadFromBytes, toJsonString, write, writeExternal
@API(help="array of IO info", direction=OUTPUT) public WaterMeterIo.IoStatsEntry[] persist_stats
public WaterMeterIo createImpl()
Schema
For 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)
Schema
fillFromImpl
in class Schema<WaterMeterIo,WaterMeterIoV3>