Class XMLSerializer
- All Implemented Interfaces:
ContentHandler
,DTDHandler
,EntityResolver
,ErrorHandler
,LexicalHandler
- Direct Known Subclasses:
HTMLSerializer
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionprotected boolean
protected Locator
protected boolean
protected int
protected Writer
protected XMLSerializer.PrefixMapping[]
protected int
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoid
characters
(char[] ch, int start, int length) Receive notification of character data.protected void
void
comment
(char[] ch, int start, int length) Report an XML comment anywhere in the document.void
endCDATA()
Report the end of a CDATA section.void
Receive notification of the end of a document.void
endDTD()
Report the end of DTD declarations.void
endElement
(String uri, String localName, String qName) Receive notification of the end of an element.void
Report the end of an entity.void
endPrefixMapping
(String prefix) End the scope of a prefix-URI mapping.protected void
escapeAttrValue
(String value) getOut()
void
ignorableWhitespace
(char[] ch, int start, int length) Receive notification of ignorable whitespace in element content.lookupPrefix
(String namespace) In-scope prefix for specifed nampespace or null.void
processingInstruction
(String target, String data) Receive notification of a processing instruction.void
setDocumentLocator
(Locator locator) Receive an object for locating the origin of SAX document events.void
void
skippedEntity
(String name) Receive notification of a skipped entity.void
Report the start of a CDATA section.void
Receive notification of the beginning of a document.void
Report the start of DTD declarations, if any.void
startElement
(String uri, String localName, String qName, Attributes atts) Receive notification of the beginning of an element.void
startEntity
(String name) Report the beginning of some internal and external XML entities.void
startPrefixMapping
(String prefix, String uri) Begin the scope of a prefix-URI Namespace mapping.Methods inherited from class org.xml.sax.helpers.DefaultHandler
error, fatalError, notationDecl, resolveEntity, unparsedEntityDecl, warning
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface org.xml.sax.ContentHandler
declaration
-
Field Details
-
m_out
-
m_documentLocator
-
m_prefixes
-
m_prefixesSize
protected int m_prefixesSize -
m_newPrefixesSize
protected int m_newPrefixesSize -
m_emptyElement
protected boolean m_emptyElement -
m_cdata
protected boolean m_cdata
-
-
Constructor Details
-
XMLSerializer
public XMLSerializer() -
XMLSerializer
-
-
Method Details
-
setDocumentLocator
Receive an object for locating the origin of SAX document events.SAX parsers are strongly encouraged (though not absolutely required) to supply a locator: if it does so, it must supply the locator to the application by invoking this method before invoking any of the other methods in the ContentHandler interface.
The locator allows the application to determine the end position of any document-related event, even if the parser is not reporting an error. Typically, the application will use this information for reporting its own errors (such as character content that does not match an application's business rules). The information returned by the locator is probably not sufficient for use with a search engine.
Note that the locator will return correct information only during the invocation of the events in this interface. The application should not attempt to use it at any other time.
- Specified by:
setDocumentLocator
in interfaceContentHandler
- Overrides:
setDocumentLocator
in classDefaultHandler
- Parameters:
locator
- An object that can return the location of any SAX document event.- See Also:
-
startDocument
Receive notification of the beginning of a document.The SAX parser will invoke this method only once, before any other event callbacks (except for
setDocumentLocator
).- Specified by:
startDocument
in interfaceContentHandler
- Overrides:
startDocument
in classDefaultHandler
- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.- See Also:
-
endDocument
Receive notification of the end of a document.The SAX parser will invoke this method only once, and it will be the last method invoked during the parse. The parser shall not invoke this method until it has either abandoned parsing (because of an unrecoverable error) or reached the end of input.
- Specified by:
endDocument
in interfaceContentHandler
- Overrides:
endDocument
in classDefaultHandler
- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.- See Also:
-
startPrefixMapping
Begin the scope of a prefix-URI Namespace mapping.The information from this event is not necessary for normal Namespace processing: the SAX XML reader will automatically replace prefixes for element and attribute names when the
http://xml.org/sax/features/namespaces
feature is true (the default).There are cases, however, when applications need to use prefixes in character data or in attribute values, where they cannot safely be expanded automatically; the start/endPrefixMapping event supplies the information to the application to expand prefixes in those contexts itself, if necessary.
Note that start/endPrefixMapping events are not guaranteed to be properly nested relative to each other: all startPrefixMapping events will occur immediately before the corresponding
startElement
event, and allendPrefixMapping
events will occur immediately after the correspondingendElement
event, but their order is not otherwise guaranteed.There should never be start/endPrefixMapping events for the "xml" prefix, since it is predeclared and immutable.
- Specified by:
startPrefixMapping
in interfaceContentHandler
- Overrides:
startPrefixMapping
in classDefaultHandler
- Parameters:
prefix
- The Namespace prefix being declared. An empty string is used for the default element namespace, which has no prefix.uri
- The Namespace URI the prefix is mapped to.- Throws:
SAXException
- The client may throw an exception during processing.- See Also:
-
endPrefixMapping
End the scope of a prefix-URI mapping.See
startPrefixMapping
for details. These events will always occur immediately after the correspondingendElement
event, but the order ofendPrefixMapping
events is not otherwise guaranteed.- Specified by:
endPrefixMapping
in interfaceContentHandler
- Overrides:
endPrefixMapping
in classDefaultHandler
- Parameters:
prefix
- The prefix that was being mapping. This is the empty string when a default mapping scope ends.- Throws:
SAXException
- The client may throw an exception during processing.- See Also:
-
startElement
public void startElement(String uri, String localName, String qName, Attributes atts) throws SAXException Receive notification of the beginning of an element.The Parser will invoke this method at the beginning of every element in the XML document; there will be a corresponding
endElement
event for every startElement event (even when the element is empty). All of the element's content will be reported, in order, before the corresponding endElement event.This event allows up to three name components for each element:
- the Namespace URI;
- the local name; and
- the qualified (prefixed) name.
Any or all of these may be provided, depending on the values of the http://xml.org/sax/features/namespaces and the http://xml.org/sax/features/namespace-prefixes properties:
- the Namespace URI and local name are required when the namespaces property is true (the default), and are optional when the namespaces property is false (if one is specified, both must be);
- the qualified name is required when the namespace-prefixes property is true, and is optional when the namespace-prefixes property is false (the default).
Note that the attribute list provided will contain only attributes with explicit values (specified or defaulted): #IMPLIED attributes will be omitted. The attribute list will contain attributes used for Namespace declarations (xmlns* attributes) only if the
http://xml.org/sax/features/namespace-prefixes
property is true (it is false by default, and support for a true value is optional).Like
characters()
, attribute values may have characters that need more than onechar
value.- Specified by:
startElement
in interfaceContentHandler
- Overrides:
startElement
in classDefaultHandler
- Parameters:
uri
- The Namespace URI, or the empty string if the element has no Namespace URI or if Namespace processing is not being performed.localName
- The local name (without prefix), or the empty string if Namespace processing is not being performed.qName
- The qualified name (with prefix), or the empty string if qualified names are not available.atts
- The attributes attached to the element. If there are no attributes, it shall be an empty Attributes object.- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.- See Also:
-
endElement
Receive notification of the end of an element.The SAX parser will invoke this method at the end of every element in the XML document; there will be a corresponding
startElement
event for every endElement event (even when the element is empty).For information on the names, see startElement.
- Specified by:
endElement
in interfaceContentHandler
- Overrides:
endElement
in classDefaultHandler
- Parameters:
uri
- The Namespace URI, or the empty string if the element has no Namespace URI or if Namespace processing is not being performed.localName
- The local name (without prefix), or the empty string if Namespace processing is not being performed.qName
- The qualified XML 1.0 name (with prefix), or the empty string if qualified names are not available.- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.
-
characters
Receive notification of character data.The Parser will call this method to report each chunk of character data. SAX parsers may return all contiguous character data in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity so that the Locator provides useful information.
The application must not attempt to read from the array outside of the specified range.
Individual characters may consist of more than one Java
char
value. There are two important cases where this happens, because characters can't be represented in just sixteen bits. In one case, characters are represented in a Surrogate Pair, using two special Unicode values. Such characters are in the so-called "Astral Planes", with a code point above U+FFFF. A second case involves composite characters, such as a base character combining with one or more accent characters.Your code should not assume that algorithms using
char
-at-a-time idioms will be working in character units; in some cases they will split characters. This is relevant wherever XML permits arbitrary characters, such as attribute values, processing instruction data, and comments as well as in data reported from this method. It's also generally relevant whenever Java code manipulates internationalized text; the issue isn't unique to XML.Note that some parsers will report whitespace in element content using the
ignorableWhitespace
method rather than this one (validating parsers must do so).- Specified by:
characters
in interfaceContentHandler
- Overrides:
characters
in classDefaultHandler
- Parameters:
ch
- The characters from the XML document.start
- The start position in the array.length
- The number of characters to read from the array.- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.- See Also:
-
ignorableWhitespace
Receive notification of ignorable whitespace in element content.Validating Parsers must use this method to report each chunk of whitespace in element content (see the W3C XML 1.0 recommendation, section 2.10): non-validating parsers may also use this method if they are capable of parsing and using content models.
SAX parsers may return all contiguous whitespace in a single chunk, or they may split it into several chunks; however, all of the characters in any single event must come from the same external entity, so that the Locator provides useful information.
The application must not attempt to read from the array outside of the specified range.
- Specified by:
ignorableWhitespace
in interfaceContentHandler
- Overrides:
ignorableWhitespace
in classDefaultHandler
- Parameters:
ch
- The characters from the XML document.start
- The start position in the array.length
- The number of characters to read from the array.- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.- See Also:
-
processingInstruction
Receive notification of a processing instruction.The Parser will invoke this method once for each processing instruction found: note that processing instructions may occur before or after the main document element.
A SAX parser must never report an XML declaration (XML 1.0, section 2.8) or a text declaration (XML 1.0, section 4.3.1) using this method.
Like
characters()
, processing instruction data may have characters that need more than onechar
value.- Specified by:
processingInstruction
in interfaceContentHandler
- Overrides:
processingInstruction
in classDefaultHandler
- Parameters:
target
- The processing instruction target.data
- The processing instruction data, or null if none was supplied. The data does not include any whitespace separating it from the target.- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.
-
skippedEntity
Receive notification of a skipped entity. This is not called for entity references within markup constructs such as element start tags or markup declarations. (The XML recommendation requires reporting skipped external entities. SAX also reports internal entity expansion/non-expansion, except within markup constructs.)The Parser will invoke this method each time the entity is skipped. Non-validating processors may skip entities if they have not seen the declarations (because, for example, the entity was declared in an external DTD subset). All processors may skip external entities, depending on the values of the
http://xml.org/sax/features/external-general-entities
and thehttp://xml.org/sax/features/external-parameter-entities
properties.- Specified by:
skippedEntity
in interfaceContentHandler
- Overrides:
skippedEntity
in classDefaultHandler
- Parameters:
name
- The name of the skipped entity. If it is a parameter entity, the name will begin with '%', and if it is the external DTD subset, it will be the string "[dtd]".- Throws:
SAXException
- Any SAX exception, possibly wrapping another exception.
-
startDTD
Report the start of DTD declarations, if any.This method is intended to report the beginning of the DOCTYPE declaration; if the document has no DOCTYPE declaration, this method will not be invoked.
All declarations reported through
DTDHandler
orDeclHandler
events must appear between the startDTD andendDTD
events. Declarations are assumed to belong to the internal DTD subset unless they appear betweenstartEntity
andendEntity
events. Comments and processing instructions from the DTD should also be reported between the startDTD and endDTD events, in their original order of (logical) occurrence; they are not required to appear in their correct locations relative to DTDHandler or DeclHandler events, however.Note that the start/endDTD events will appear within the start/endDocument events from ContentHandler and before the first
startElement
event.- Specified by:
startDTD
in interfaceLexicalHandler
- Parameters:
name
- The document type name.publicId
- The declared public identifier for the external DTD subset, or null if none was declared.systemId
- The declared system identifier for the external DTD subset, or null if none was declared. (Note that this is not resolved against the document base URI.)- Throws:
SAXException
- The application may raise an exception.- See Also:
-
endDTD
Report the end of DTD declarations.This method is intended to report the end of the DOCTYPE declaration; if the document has no DOCTYPE declaration, this method will not be invoked.
- Specified by:
endDTD
in interfaceLexicalHandler
- Throws:
SAXException
- The application may raise an exception.- See Also:
-
startEntity
Report the beginning of some internal and external XML entities.The reporting of parameter entities (including the external DTD subset) is optional, and SAX2 drivers that report LexicalHandler events may not implement it; you can use the
http://xml.org/sax/features/lexical-handler/parameter-entities
feature to query or control the reporting of parameter entities.General entities are reported with their regular names, parameter entities have '%' prepended to their names, and the external DTD subset has the pseudo-entity name "[dtd]".
When a SAX2 driver is providing these events, all other events must be properly nested within start/end entity events. There is no additional requirement that events from
DeclHandler
orDTDHandler
be properly ordered.Note that skipped entities will be reported through the
skippedEntity
event, which is part of the ContentHandler interface.Because of the streaming event model that SAX uses, some entity boundaries cannot be reported under any circumstances:
- general entities within attribute values
- parameter entities within declarations
These will be silently expanded, with no indication of where the original entity boundaries were.
Note also that the boundaries of character references (which are not really entities anyway) are not reported.
All start/endEntity events must be properly nested.
- Specified by:
startEntity
in interfaceLexicalHandler
- Parameters:
name
- The name of the entity. If it is a parameter entity, the name will begin with '%', and if it is the external DTD subset, it will be "[dtd]".- Throws:
SAXException
- The application may raise an exception.- See Also:
-
endEntity
Report the end of an entity.- Specified by:
endEntity
in interfaceLexicalHandler
- Parameters:
name
- The name of the entity that is ending.- Throws:
SAXException
- The application may raise an exception.- See Also:
-
startCDATA
Report the start of a CDATA section.The contents of the CDATA section will be reported through the regular
characters
event; this event is intended only to report the boundary.- Specified by:
startCDATA
in interfaceLexicalHandler
- Throws:
SAXException
- The application may raise an exception.- See Also:
-
endCDATA
Report the end of a CDATA section.- Specified by:
endCDATA
in interfaceLexicalHandler
- Throws:
SAXException
- The application may raise an exception.- See Also:
-
comment
Report an XML comment anywhere in the document.This callback will be used for comments inside or outside the document element, including comments in the external DTD subset (if read). Comments in the DTD must be properly nested inside start/endDTD and start/endEntity events (if used).
- Specified by:
comment
in interfaceLexicalHandler
- Parameters:
ch
- An array holding the characters in the comment.start
- The starting position in the array.length
- The number of characters to use from the array.- Throws:
SAXException
- The application may raise an exception.
-
getOut
-
setOut
-
getDocumentLocator
-
lookupPrefix
In-scope prefix for specifed nampespace or null. -
closeStartElement
- Throws:
SAXException
-
escapeAttrValue
- Throws:
SAXException
-