|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--org.apache.commons.configuration.AbstractConfiguration | +--org.apache.commons.configuration.HierarchicalConfiguration
A specialized configuration class that extends its base class by the ability of keeping more structure in the stored properties.
There
are some sources of configuration data that cannot be stored very well in a
BaseConfiguration
object because then their structure is lost.
This is especially true for XML documents. This class can deal with such
structured configuration sources by storing the properties in a tree-like
organization.
The internal used storage form allows for a more sophisticated access to single properties. As an example consider the following XML document:
<database> <tables> <table> <name>users</name> <fields> <field> <name>lid</name> <type>long</name> </field> <field> <name>usrName</name> <type>java.lang.String</type> </field> ... </fields> </table> <table> <name>documents</name> <fields> <field> <name>docid</name> <type>long</type> </field> ... </fields> </table> ... </tables> </database>
If this document is parsed and stored in a
HierarchicalConfiguration
object (which can be done by one of
the sub classes), there are enhanced possibilities of accessing properties.
The keys for querying information can contain indices that select a certain
element if there are multiple hits.
For instance the key
tables.table(0).name
can be used to find out the name of the
first table. In opposite tables.table.name
would return a
collection with the names of all available tables. Similarily the key
tables.table(1).fields.field.name
returns a collection with
the names of all fields of the second table. If another index is added after
the field
element, a single field can be accessed:
tables.table(1).fields.field(0).name
.
There is a
getMaxIndex()
method that returns the maximum allowed index
that can be added to a given property key. This method can be used to iterate
over all values defined for a certain property.
Inner Class Summary | |
protected static class |
HierarchicalConfiguration.BuilderVisitor
A specialized visitor base class that can be used for storing the tree of configuration nodes. |
static class |
HierarchicalConfiguration.Node
A data class for storing (hierarchical) property information. |
static class |
HierarchicalConfiguration.NodeVisitor
Definition of a visitor class for traversing a node and all of its children.This class defines the interface of a visitor for Node objects and provides a default implementation. |
Fields inherited from class org.apache.commons.configuration.AbstractConfiguration |
END_TOKEN, START_TOKEN |
Constructor Summary | |
HierarchicalConfiguration()
|
Method Summary | |
void |
addNodes(String key,
Collection nodes)
Adds a collection of nodes at the specified position of the configuration tree. |
protected void |
addPropertyDirect(String key,
Object obj)
Adds the property with the specified key.To be able to deal with the structure supported by this configuration implementation the passed in key is of importance, especially the indices it might contain. |
protected void |
clearNode(HierarchicalConfiguration.Node node)
Clears the value of the specified node. |
void |
clearProperty(String key)
Removes the property with the given key. |
void |
clearTree(String key)
Removes all values of the property with the given name and of keys that start with this name. |
Object |
clone()
Creates a copy of this object. |
boolean |
containsKey(String key)
Checks if the specified key is contained in this configuration. |
protected HierarchicalConfiguration.Node |
createAddPath(ConfigurationKey.KeyIterator keyIt,
HierarchicalConfiguration.Node root)
Creates the missing nodes for adding a new property. |
protected HierarchicalConfiguration.Node |
createNode(String name)
Creates a new Node object with the specified name. |
protected HierarchicalConfiguration.Node |
fetchAddNode(ConfigurationKey.KeyIterator keyIt,
HierarchicalConfiguration.Node startNode)
Returns a reference to the parent node of an add operation. |
protected List |
fetchNodeList(String key)
Helper method for fetching a list of all nodes that are addressed by the specified key. |
protected HierarchicalConfiguration.Node |
findLastPathNode(ConfigurationKey.KeyIterator keyIt,
HierarchicalConfiguration.Node node)
Finds the last existing node for an add operation. |
protected void |
findPropertyNodes(ConfigurationKey.KeyIterator keyPart,
HierarchicalConfiguration.Node node,
Collection nodes)
Recursive helper method for fetching a property. |
Iterator |
getKeys()
Returns an iterator with all keys defined in this configuration. |
Iterator |
getKeys(String prefix)
Returns an iterator with all keys defined in this configuration that start with the given prefix. |
int |
getMaxIndex(String key)
Returns the maximum defined index for the given key. |
Object |
getProperty(String key)
Fetches the specified property. |
HierarchicalConfiguration.Node |
getRoot()
Returns the root node of this hierarchical configuration. |
boolean |
isEmpty()
Checks if this configuration is empty. |
protected boolean |
nodeDefined(HierarchicalConfiguration.Node node)
Checks if the specified node is defined. |
protected void |
removeNode(HierarchicalConfiguration.Node node)
Removes the specified node from this configuration. |
void |
setProperty(String key,
Object value)
Sets the value of the specified property. |
void |
setRoot(HierarchicalConfiguration.Node node)
Sets the root node of this hierarchical configuration. |
Configuration |
subset(String prefix)
Creates a new Configuration object containing all keys
that start with the specified prefix. |
Methods inherited from class org.apache.commons.configuration.AbstractConfiguration |
addProperty, clear, getBigDecimal, getBigDecimal, getBigInteger, getBigInteger, getBoolean, getBoolean, getBoolean, getByte, getByte, getByte, getDelimiter, getDouble, getDouble, getDouble, getFloat, getFloat, getFloat, getInt, getInt, getInteger, getList, getList, getLong, getLong, getLong, getProperties, getProperties, getShort, getShort, getShort, getString, getString, getStringArray, interpolate, interpolate, interpolateHelper, isThrowExceptionOnMissing, resolveContainerStore, setDelimiter, setThrowExceptionOnMissing |
Methods inherited from class java.lang.Object |
equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
public HierarchicalConfiguration()
Method Detail |
public HierarchicalConfiguration.Node getRoot()
public void setRoot(HierarchicalConfiguration.Node node)
node
- the root nodepublic Object getProperty(String key)
key
- the key to be looked upprotected void addPropertyDirect(String key, Object obj)
Adds the property with the specified key.
To be able to deal with the structure supported by this configuration implementation the passed in key is of importance, especially the indices it might contain. The following example should clearify this: Suppose the actual configuration contains the following elements:
tables +-- table +-- name = user +-- fields +-- field +-- name = uid +-- field +-- name = firstName ... +-- table +-- name = documents +-- fields ...
In this example a database structure is defined, e.g. all fields
of the first table could be accessed using the key
tables.table(0).fields.field.name
. If now properties are
to be added, it must be exactly specified at which position in the
hierarchy the new property is to be inserted. So to add a new field name
to a table it is not enough to say just
config.addProperty("tables.table.fields.field.name", "newField");
The statement given above contains some ambiguity. For instance
it is not clear, to which table the new field should be added. If this
method finds such an ambiguity, it is resolved by following the last
valid path. Here this would be the last table. The same is true for the
field
; because there are multiple fields and no explicit
index is provided, a new name
property would be added to
the last field - which is propably not what was desired.
To make
things clear explicit indices should be provided whenever possible. In
the example above the exact table could be specified by providing an
index for the table
element as in
tables.table(1).fields
. By specifying an index it can
also be expressed that at a given position in the configuration tree a
new branch should be added. In the example above we did not want to add
an additional name
element to the last field of the table,
but we want a complete new field
element. This can be
achieved by specifying an invalid index (like -1) after the element where
a new branch should be created. Given this our example would run:
config.addProperty("tables.table(1).fields.field(-1).name", "newField");
With this notation it is possible to add new branches
everywhere. We could for instance create a new table
element by specifying
config.addProperty("tables.table(-1).fields.field.name", "newField2");
(Note that because after the table
element a new
branch is created indices in following elements are not relevant; the
branch is new so there cannot be any ambiguities.)
addPropertyDirect
in class AbstractConfiguration
key
- the key of the new propertyobj
- the value of the new propertypublic void addNodes(String key, Collection nodes)
addProperty()
, but
instead of a single property a whole collection of nodes can be added -
and thus complete configuration sub trees. E.g. with this method it is
possible to add parts of another HierarchicalConfiguration
object to this object.key
- the key where the nodes are to be added; can be null ,
then they are added to the root nodenodes
- a collection with the Node
objects to be
addedpublic boolean isEmpty()
isEmpty
in class AbstractConfiguration
public Configuration subset(String prefix)
Configuration
object containing all keys
that start with the specified prefix. This implementation will return a
HierarchicalConfiguration
object so that the structure of
the keys will be saved.subset
in class AbstractConfiguration
prefix
- the prefix of the keys for the subsetpublic boolean containsKey(String key)
containsKey
in class AbstractConfiguration
key
- the key to be chekcedpublic void setProperty(String key, Object value)
setProperty
in class AbstractConfiguration
key
- the key of the property to setvalue
- the new value of this propertypublic void clearTree(String key)
clearTree("foo")
would remove both properties.key
- the key of the property to be removedpublic void clearProperty(String key)
clearProperty
in class AbstractConfiguration
key
- the key of the property to be removedpublic Iterator getKeys()
getKeys
in class AbstractConfiguration
public Iterator getKeys(String prefix)
getKeys
in class AbstractConfiguration
prefix
- the prefix of the keys to start withpublic int getMaxIndex(String key)
key
- the key to be checkedpublic Object clone()
clone
in class Object
protected List fetchNodeList(String key)
key
- the keyprotected void findPropertyNodes(ConfigurationKey.KeyIterator keyPart, HierarchicalConfiguration.Node node, Collection nodes)
keyPart
- the configuration key iteratornode
- the actual nodenodes
- here the found nodes are storedprotected boolean nodeDefined(HierarchicalConfiguration.Node node)
node
- the node to be checkedprotected void removeNode(HierarchicalConfiguration.Node node)
node
- the node to be removedprotected void clearNode(HierarchicalConfiguration.Node node)
node
- the node to be cleardprotected HierarchicalConfiguration.Node fetchAddNode(ConfigurationKey.KeyIterator keyIt, HierarchicalConfiguration.Node startNode)
keyIt
- the iterator for the key of the new propertystartNode
- the node to start the search withprotected HierarchicalConfiguration.Node findLastPathNode(ConfigurationKey.KeyIterator keyIt, HierarchicalConfiguration.Node node)
keyIt
- the key iteratornode
- the actual nodeprotected HierarchicalConfiguration.Node createAddPath(ConfigurationKey.KeyIterator keyIt, HierarchicalConfiguration.Node root)
keyIt
- the key iteratorroot
- the base node of the path to be createdprotected HierarchicalConfiguration.Node createNode(String name)
Node
object with the specified name. This
method can be overloaded in derived classes if a specific node type is
needed. This base implementation always returns a new object of the
Node
class.name
- the name of the new node
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |