s.fr/framework-ldap/configuration.dtd.
This implantation can handle the following tags:
- mapper-config
- Root tag
- var
- A variable declaration. Later occurence of this variable will be replaced the given value
- mapper-subconfig
- Declares the class of a subconfigurator that can later be invoked. Attribute
class
must be a valid class name which can be instantiated without parameters and attribute namespace
a string denoting the namespace of this configurator.
Sub-classes can override all content handler methods but not {@link #characters(char[],int,int)} which handles variables substitution.Method {@link #getBuffer()} should be used instead to retrieve text nodes'content.
Variables can be used in the source XML file. These variables are syntactic: if var
is the name of a variable defined in this configurator, then all occurences of the string ${var}
in the source XML file are replaced by the value of the variable. All variables substitution occurs in attributes values and in text nodes before they are passed to the subconfigurators.
A DTD (base-configuration.dtd
) is provided for base tags handled by this configurator but as other fragments may be included, it does only include the few tags directly managed by this class. Other DTDs can be included following the pattern given in framework-ldap.dtd
. The parser can be set in validating mode using {@link #setValidating(boolean)} method, in which case all syntax errors willgive rise to a parsing exception and stops processing.
The various parse methods may be called several times as configuration may be split between various locations. Once the method {@link #configure(Configure)}has been called and has returned correctly, client may assume that configuration state is cleared so calls to this method may be interspersed with calls to parse()
methods.
@author nono
@version $Id: XMLConfigurator.java 212 2005-11-17 15:19:21Z/C=FR/ST=Nord/L=Lille/O=Norsys SA/OU=UE/CN=Arnaud Bailly/emailAddress=abailly@norsys.fr $
@see
DTD for base tags