java.lang.Object org.xml.sax.helpers.NamespaceSupportEncapsulate Namespace logic for use by applications using SAX, or internally by SAX drivers.
This module, both source code and documentation, is in the Public Domain, and comes with NO WARRANTY. See http://www.saxproject.org for further information.
This class encapsulates the logic of Namespace processing: it tracks the declarations currently in force for each context and automatically processes qualified XML names into their Namespace parts; it can also be used in reverse for generating XML qnames from Namespaces.
Namespace support objects are reusable, but the reset method must be invoked between each session.
Here is a simple session:
String parts = new String; NamespaceSupport support = new NamespaceSupport(); support.pushContext(); support.declarePrefix("", "http://www.w3.org/1999/xhtml"); support.declarePrefix("dc", "http://www.purl.org/dc#"); parts = support.processName("p", parts, false); System.out.println("Namespace URI: " + parts); System.out.println("Local name: " + parts); System.out.println("Raw name: " + parts); parts = support.processName("dc:title", parts, false); System.out.println("Namespace URI: " + parts); System.out.println("Local name: " + parts); System.out.println("Raw name: " + parts); support.popContext();
Note that this class is optimized for the use case where most elements do not contain Namespace declarations: if the same prefix/URI mapping is repeated for each context (for example), this class will be somewhat less efficient.
Although SAX drivers (parsers) may choose to use this class to implement namespace handling, they are not required to do so. Applications must track namespace information themselves if they want to use namespace information.
|Nested Class Summary:|
|final class||NamespaceSupport.Context||Internal class for a single Namespace context.
This module caches and reuses Namespace contexts, so the number allocated will be equal to the element depth of the document, not to the total number of elements (i.e. 5-10 rather than tens of thousands). Also, data structures used to represent contexts are shared when possible (child contexts without declarations) to further reduce the amount of memory that's consumed.
|public static final String||XMLNS||The XML Namespace URI as a constant.
The value is |
This is the Namespace URI that is automatically mapped to the "xml" prefix.
|public static final String||NSDECL||The namespace declaration URI as a constant.
The value is |
This is the Namespace URI that is optionally applied to xmlns and xmlns:* attributes, which are used to declare namespaces.
|Method from org.xml.sax.helpers.NamespaceSupport Summary:|
|declarePrefix, getDeclaredPrefixes, getPrefix, getPrefixes, getPrefixes, getURI, isNamespaceDeclUris, popContext, processName, pushContext, reset, setNamespaceDeclUris|
|Methods from java.lang.Object:|
|clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait|
|Method from org.xml.sax.helpers.NamespaceSupport Detail:|
public boolean declarePrefix(String prefix, String uri)
This method declares a prefix in the current Namespace context; the prefix will remain in force until this context is popped, unless it is shadowed in a descendant context.
To declare the default element Namespace, use the empty string as the prefix.
Note that there is an asymmetry in this library: getPrefix will not return the "" prefix, even if you have declared a default element namespace. To check for a default namespace, you have to look it up explicitly using getURI . This asymmetry exists to make it easier to look up prefixes for attribute names, where the default prefix is not allowed.
public Enumeration getDeclaredPrefixes()
The empty (default) prefix will be included in this enumeration; note that this behaviour differs from that of #getPrefix and #getPrefixes .
public String getPrefix(String uri)
If more than one prefix is currently mapped to the same URI, this method will make an arbitrary selection; if you want all of the prefixes, use the #getPrefixes method instead.
Note: this will never return the empty (default) prefix; to check for a default prefix, use the getURI method with an argument of "".
public Enumeration getPrefixes()
Note: if there is a default prefix, it will not be returned in this enumeration; check for the default prefix using the getURI with an argument of "".
public Enumeration getPrefixes(String uri)
This method returns prefixes mapped to a specific Namespace URI. The xml: prefix will be included. If you want only one prefix that's mapped to the Namespace URI, and you don't care which one you get, use the getPrefix method instead.
Note: the empty (default) prefix is never included in this enumeration; to check for the presence of a default Namespace, use the getURI method with an argument of "".
public String getURI(String prefix)
This method looks up the prefix in the current context. Use the empty string ("") for the default Namespace.
public boolean isNamespaceDeclUris()
public void popContext()
Normally, you should pop the context at the end of each XML element. After popping the context, all Namespace prefix mappings that were previously in force are restored.
You must not attempt to declare additional Namespace prefixes after popping a context, unless you push another context first.
public String processName(String qName, String parts, boolean isAttribute)
This method processes a raw XML qualified name in the current context by removing the prefix and looking it up among the prefixes currently declared. The return value will be the array supplied by the caller, filled in as follows:
All of the strings in the array will be internalized. If the raw name has a prefix that has not been declared, then the return value will be null.
Note that attribute names are processed differently than element names: an unprefixed element name will receive the default Namespace (if any), while an unprefixed attribute name will not.
public void pushContext()
Event callback code should start a new context once per element. This means being ready to call this in either of two places. For elements that don't include namespace declarations, the ContentHandler.startElement() callback is the right place. For elements with such a declaration, it'd done in the first ContentHandler.startPrefixMapping() callback. A boolean flag can be used to track whether a context has been started yet. When either of those methods is called, it checks the flag to see if a new context needs to be started. If so, it starts the context and sets the flag. After ContentHandler.startElement() does that, it always clears the flag.
Normally, SAX drivers would push a new context at the beginning of each XML element. Then they perform a first pass over the attributes to process all namespace declarations, making ContentHandler.startPrefixMapping() callbacks. Then a second pass is made, to determine the namespace-qualified names for all attributes and for the element name. Finally all the information for the ContentHandler.startElement() callback is available, so it can then be made.
The Namespace support object always starts with a base context already in force: in this context, only the "xml" prefix is declared.
public void reset()
It is necessary to invoke this method before reusing the Namespace support object for a new session. If namespace declaration URIs are to be supported, that flag must also be set to a non-default value.
public void setNamespaceDeclUris(boolean value)