Class NoOpHandler
- All Implemented Interfaces:
ContentHandler
,DTDHandler
,EntityResolver
,ErrorHandler
,LexicalHandler
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoid
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
endDTD()
Report the end of DTD declarations.void
Report the end of an entity.void
Report the start of a CDATA section.void
Report the start of DTD declarations, if any.void
startEntity
(String name) Report the beginning of some internal and external XML entities.Methods inherited from class org.xml.sax.helpers.DefaultHandler
characters, endDocument, endElement, endPrefixMapping, error, fatalError, ignorableWhitespace, notationDecl, processingInstruction, resolveEntity, setDocumentLocator, skippedEntity, startDocument, startElement, startPrefixMapping, 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
-
Constructor Details
-
NoOpHandler
public NoOpHandler()
-
-
Method Details
-
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.
-