| Interface | Description |
|---|---|
| ConfigurationBackend |
Interface for backends that can read and (optionally) write values at given
attribute names.
|
| ExtendedConfigurationBackend |
The extended configuration backend allows a backend to specify ways to
retrieve other types than strings.
|
| Parser<T> |
Interface for abstract object parsers.
|
| Value<T> |
Wrapper for a configuration value.
|
| Class | Description |
|---|---|
| AbstractValue<T> |
An abstract implementation of a
Value. |
| BooleanValue |
A wrapper around a boolean value.
|
| CachingConfigurationBackend |
Configuration backend proxy that caches the attribute values it retrieves.
|
| Configuration |
A configuration contains all necessary methods to read integral data types
from a
ConfigurationBackend. |
| DoubleValue |
A wrapper around a double value.
|
| IntegerValue |
A wrapper around an integer value.
|
| LongValue |
A wrapper around a long value.
|
| MapConfigurationBackend |
Configuration backend that is backed by a
Map. |
| ReadOnlyValue<T> |
Implementation of a read-only value that never changes.
|
| StringValue |
A wrapper around a string value.
|
| XMLConfigurationBackend |
Configuration backend that reads and writes its configuration from/to an XML
file.
|
| Exception | Description |
|---|---|
| AttributeNotFoundException |
Exception that will be thrown when a non-existing attribute is requested.
|
| ConfigurationException |
Parent exception for all exceptions that can occur during configuration file
parsing.
|
| ValueFormatException |
Exception that signals a conversion error if a specified format for a value
is requested.
|
ConfigurationBackend for the
configuration you want to access. Using the configuration backend you can
then create the Configuration and start reading
integral data types from it. By writing specialized parsers you can handle
more abstract objects (e.g. for databases or message connectors) as well.Copyright © 2026. All rights reserved.