org.xml.sax.helpers

Class NamespaceSupport

public class NamespaceSupport extends Object

Encapsulate 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 1.0 names into their Namespace parts; it can also be used in reverse for generating XML 1.0 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[3];
 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[0]);
 System.out.println("Local name: " + parts[1]);
 System.out.println("Raw name: " + parts[2]);

 parts = support.processName("dc:title", parts, false);
 System.out.println("Namespace URI: " + parts[0]);
 System.out.println("Local name: " + parts[1]);
 System.out.println("Raw name: " + parts[2]);

 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.

Since: SAX 2.0

Version: 2.0.1 (sax2r2)

Author: David Megginson

Field Summary
static StringXMLNS
The XML Namespace URI as a constant.
Constructor Summary
NamespaceSupport()
Create a new Namespace support object.
Method Summary
booleandeclarePrefix(String prefix, String uri)
Declare a Namespace prefix.
EnumerationgetDeclaredPrefixes()
Return an enumeration of all prefixes declared in this context.
StringgetPrefix(String uri)
Return one of the prefixes mapped to a Namespace URI.
EnumerationgetPrefixes()
Return an enumeration of all prefixes currently declared.
EnumerationgetPrefixes(String uri)
Return an enumeration of all prefixes currently declared for a URI.
StringgetURI(String prefix)
Look up a prefix and get the currently-mapped Namespace URI.
voidpopContext()
Revert to the previous Namespace context.
String[]processName(String qName, String[] parts, boolean isAttribute)
Process a raw XML 1.0 name, after all declarations in the current context have been handled by declarePrefix().
voidpushContext()
Start a new Namespace context.
voidreset()
Reset this Namespace support object for reuse.

Field Detail

XMLNS

public static final String XMLNS
The XML Namespace URI as a constant. The value is http://www.w3.org/XML/1998/namespace as defined in the XML Namespaces specification.

This is the Namespace URI that is automatically mapped to the "xml" prefix.

Constructor Detail

NamespaceSupport

public NamespaceSupport()
Create a new Namespace support object.

Method Detail

declarePrefix

public boolean declarePrefix(String prefix, String uri)
Declare a Namespace prefix. All prefixes must be declared before they are referenced. For example, a SAX driver (parser) would scan an element's attributes in two passes: first for namespace declarations, then a second pass using processName() to interpret prefixes against (potentially redefined) prefixes.

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 you must not declare a prefix after you've pushed and popped another Namespace context, or treated the declarations phase as complete by processing a prefixed name.

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.

Parameters: prefix The prefix to declare, or the empty string to indicate the default element namespace. This may never have the value "xml" or "xmlns". uri The Namespace URI to associate with the prefix.

Returns: true if the prefix was legal, false otherwise

Throws: IllegalStateException when a prefix is declared after looking up a name in the context, or after pushing another context on top of it.

See Also: NamespaceSupport NamespaceSupport NamespaceSupport

getDeclaredPrefixes

public Enumeration getDeclaredPrefixes()
Return an enumeration of all prefixes declared in this context.

The empty (default) prefix will be included in this enumeration; note that this behaviour differs from that of NamespaceSupport and NamespaceSupport.

Returns: An enumeration of all prefixes declared in this context.

See Also: NamespaceSupport NamespaceSupport

getPrefix

public String getPrefix(String uri)
Return one of the prefixes mapped to a Namespace 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 NamespaceSupport 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 "".

Parameters: uri The Namespace URI. isAttribute true if this prefix is for an attribute (and the default Namespace is not allowed).

Returns: One of the prefixes currently mapped to the URI supplied, or null if none is mapped or if the URI is assigned to the default Namespace.

See Also: NamespaceSupport NamespaceSupport

getPrefixes

public Enumeration getPrefixes()
Return an enumeration of all prefixes currently declared.

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 "".

Returns: An enumeration of all prefixes declared in the current context except for the empty (default) prefix.

See Also: NamespaceSupport NamespaceSupport

getPrefixes

public Enumeration getPrefixes(String uri)
Return an enumeration of all prefixes currently declared for a 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 "".

Parameters: uri The Namespace URI.

Returns: An enumeration of all prefixes declared in the current context.

See Also: NamespaceSupport NamespaceSupport NamespaceSupport

getURI

public String getURI(String prefix)
Look up a prefix and get the currently-mapped Namespace URI.

This method looks up the prefix in the current context. Use the empty string ("") for the default Namespace.

Parameters: prefix The prefix to look up.

Returns: The associated Namespace URI, or null if the prefix is undeclared in this context.

See Also: NamespaceSupport NamespaceSupport

popContext

public void popContext()
Revert to the previous Namespace context.

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.

See Also: NamespaceSupport

processName

public String[] processName(String qName, String[] parts, boolean isAttribute)
Process a raw XML 1.0 name, after all declarations in the current context have been handled by declarePrefix().

This method processes a raw XML 1.0 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:

parts[0]
The Namespace URI, or an empty string if none is in use.
parts[1]
The local name (without prefix).
parts[2]
The original raw name.

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 received the default Namespace (if any), while an unprefixed attribute name will not.

Parameters: qName The raw XML 1.0 name to be processed. parts An array supplied by the caller, capable of holding at least three members. isAttribute A flag indicating whether this is an attribute name (true) or an element name (false).

Returns: The supplied array holding three internalized strings representing the Namespace URI (or empty string), the local name, and the raw XML 1.0 name; or null if there is an undeclared prefix.

See Also: NamespaceSupport java.lang.String#intern

pushContext

public void pushContext()
Start a new Namespace context. The new context will automatically inherit the declarations of its parent context, but it will also keep track of which declarations were made within this context.

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.

See Also: ContentHandler NamespaceSupport

reset

public void reset()
Reset this Namespace support object for reuse.

It is necessary to invoke this method before reusing the Namespace support object for a new session.