public final class DfsConfig extends StoredConfig
The current implementation acts as if there is no persistent storage: loading simply clears the config, and saving does nothing.
Config.ConfigEnum, Config.SectionParser<T>| Constructor and Description |
|---|
DfsConfig() |
| Modifier and Type | Method and Description |
|---|---|
void |
load()
Load the configuration from the persistent store.
|
void |
save()
Save the configuration to the persistent store.
|
clearaddChangeListener, fireConfigChangedEvent, fromText, get, getBoolean, getBoolean, getEnum, getEnum, getInt, getInt, getLong, getLong, getNames, getNames, getNames, getNames, getRefSpecs, getSections, getString, getStringList, getSubsections, getTimeUnit, isMissing, isUtf8, notifyUponTransientChanges, readIncludedConfig, setBoolean, setEnum, setInt, setLong, setString, setStringList, setTypedConfigGetter, toText, uncache, unset, unsetSectionpublic void load()
throws java.io.IOException,
ConfigInvalidException
If the configuration does not exist, this configuration is cleared, and thus behaves the same as though the backing store exists, but is empty.
load in class StoredConfigjava.io.IOException - the configuration could not be read (but does exist).ConfigInvalidException - the configuration is not properly formatted.public void save()
throws java.io.IOException
save in class StoredConfigjava.io.IOException - the configuration could not be written.