public static interface ConfigurationDescription.ConfigurationEntry extends UserAttributeContainer, PluginDataContainer
A configuration value may be of any data type that is also allowed for a data element in a process. This allows to retrieve a configuration value dynamically at runtime from a data element of the corresponding process instead of providing it statically while modelling.
| Modifier and Type | Method and Description |
|---|---|
ProcessConstants.AdeptDataType |
getDataType()
Gets the data type of the configuration entry, which is an
AdeptDataType. |
java.lang.String |
getDescription()
Gets a user-friendly description (including its localisation) for a
configuration entry.
|
java.lang.String |
getName()
Gets the unique (with respect to the configuration description hierarchy,
that is the parent configuration descriptions) name of this entry.
|
java.lang.String[] |
getRestrictions()
Gets the
restrictions
that apply to this configuration entry value. |
boolean |
isOptional()
Gets whether this configuration entry is optional and is therefore not
needed at runtime by the corresponding executable component.
|
getUserAttributes, getUserAttributeValue, removeUserAttributeValue, setUserAttributeValuegetPluginData, getPluginDatas, getSupportedPluginsjava.lang.String getName()
java.lang.String getDescription()
ProcessConstants.AdeptDataType getDataType()
AdeptDataType. This allows to mix parameter values and
configuration values. However, since configurations are usually based on
simple strings, implementations of Configurations need to
provide appropriate conversion methods between these types and a string
representation thereof. This is also crucial when editing the
corresponding configuration file or setting the configuration value via
a string type (ChangeableConfiguration.setString(String, String))!boolean isOptional()
java.lang.String[] getRestrictions()
restrictions
that apply to this configuration entry value. The restriction allows for
some more type-safety when handling configuration values that may stem
from simple string-based configuration files.restrictions
that apply to the configuration entry value. These allow for more
type-safety, especially for string-based configuration files.