ConfigurationReader-object, then it should be used to read the configuration data.See: Description
| Interface | Description |
|---|---|
| Configurable |
An special kind of object that can be created (and whose state can be loaded) from configuration data.
At the moment of configuration loading, all loaded EcmConfigurable objects will be validated. |
| Configuration |
Description of "Configuration", i.
|
| ConfigurationParameter | |
| ConfigurationProcessor |
An object that performs processing of configuration data.
ConfigurationProcessors are used after a configuration is loaded, in order to (if wanted) inject some configuration data into managers, service providers or some other application objects. |
| ConfigurationReader |
An object that reads configuration data from the configuration files.
|
| Class | Description |
|---|---|
| AbstractConfigurable |
An object that (if wanted/needed) simplifies the creation of
Configurable.It performs standard attribute-mutation operations (any non-trivial mutation should be performed in inherited classes). The way aforementioned attribute-mutation is performed does violate the encapsulation principle ... |
| ConfigurationManager |
Configuration information provider for the rest of the library.
As soon as it receives (any) request for configuration data, it loads them, process them and (later on) just responds on subsequent requests. |
| ConfigurationReaderDefault |
| Exception | Description |
|---|---|
| ConfigurationException |
Specific kind of exception, limited to situations where configuration data are logically invalid.
|
ConfigurationReader-object, then it should be used to read the configuration data.
If no ConfigurationReader-object is available, then we will react as if there is no specific configuration data.