ContentHandler
interface, which includes Namespace support.
public interface DocumentHandler
Receive notification of general document events.
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 was the main event-handling interface for SAX1; in
SAX2, it has been replaced by ContentHandler, which provides Namespace support and reporting
of skipped entities. This interface is included in SAX2 only
to support legacy SAX1 applications.
The order of events in this interface is very important, and mirrors the order of information in the document itself. For example, all of an element's content (character data, processing instructions, and/or subelements) will appear, in order, between the startElement event and the corresponding endElement event.
Application writers who do not want to implement the entire interface can derive a class from HandlerBase, which implements the default functionality; parser writers can instantiate HandlerBase to obtain a default handler. The application can find the location of any document event using the Locator interface supplied by the Parser through the setDocumentLocator method.
Parser.setDocumentHandler(org.xml.sax.DocumentHandler),
Locator,
HandlerBase| Method Summary | |
|---|---|
void |
characters(char[] ch,
int start,
int length)
Deprecated. Receive notification of character data. |
void |
endDocument()
Deprecated. Receive notification of the end of a document. |
void |
endElement(String name)
Deprecated. Receive notification of the end of an element. |
void |
ignorableWhitespace(char[] ch,
int start,
int length)
Deprecated. Receive notification of ignorable whitespace in element content. |
void |
processingInstruction(String target,
String data)
Deprecated. Receive notification of a processing instruction. |
void |
setDocumentLocator(Locator locator)
Deprecated. Receive an object for locating the origin of SAX document events. |
void |
startDocument()
Deprecated. Receive notification of the beginning of a document. |
void |
startElement(String name,
AttributeList atts)
Deprecated. Receive notification of the beginning of an element. |
| Method Detail |
|---|
void setDocumentLocator(Locator locator)
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 DocumentHandler 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.
locator - An object that can return the location of
any SAX document event.Locator
void startDocument()
throws SAXException
The SAX parser will invoke this method only once, before any other methods in this interface or in DTDHandler (except for setDocumentLocator).
SAXException - Any SAX exception, possibly
wrapping another exception.
void endDocument()
throws SAXException
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.
SAXException - Any SAX exception, possibly
wrapping another exception.void startElement(String name, AttributeList atts) throws SAXException
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.
If the element name has a namespace prefix, the prefix will still be attached. Note that the attribute list provided will contain only attributes with explicit values (specified or defaulted): #IMPLIED attributes will be omitted.
name - The element type name.atts - The attributes attached to the element, if any.
SAXException - Any SAX exception, possibly
wrapping another exception.endElement(java.lang.String),
AttributeListvoid endElement(String name) throws SAXException
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).
If the element name has a namespace prefix, the prefix will still be attached to the name.
name - The element type name
SAXException - Any SAX exception, possibly
wrapping another exception.
void characters(char[] ch,
int start,
int length)
throws SAXException
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.
Note that some parsers will report whitespace using the ignorableWhitespace() method rather than this one (validating parsers must do so).
ch - The characters from the XML document.start - The start position in the array.length - The number of characters to read from the array.
SAXException - Any SAX exception, possibly
wrapping another exception.ignorableWhitespace(char[], int, int),
Locator
void ignorableWhitespace(char[] ch,
int start,
int length)
throws SAXException
Validating Parsers must use this method to report each chunk of ignorable whitespace (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.
ch - The characters from the XML document.start - The start position in the array.length - The number of characters to read from the array.
SAXException - Any SAX exception, possibly
wrapping another exception.characters(char[], int, int)void processingInstruction(String target, String data) throws SAXException
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 should 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.
target - The processing instruction target.data - The processing instruction data, or null if
none was supplied.
SAXException - Any SAX exception, possibly
wrapping another exception.Ces informations proviennent du site de http://java.sun.com
Le contenu de cette page provient du site de Sun, et est généré depuis un cache sur l'infobrol après certains traitements automatisés. La présentation peut donc différer du document original, mais le contenu aussi. Vous pouvez utiliser ce bouton pour afficher la page originale du site de Sun :
Maintenir les pages en cache sur différents sites peut offrir plus de disponibilité.
Chaque page est indexée dans la base de donnée, ce qui permet de retrouver facilement les informations, au moyen des sommaires, du moteur de recherche interne, etc.
Des facilités sont mises en place pour que les membres de l'infobrol puissent effectuer des traductions en français des différents documents. Ceci devrait permettre aux débutants en programmation Java de consulter les API en français s'ils maîtrisent moins bien la langue de Shakespeare. Dans le cas où une traduction a été soumise, elle est disponible au moyen d'un lien en bas de page. Si la traduction a été validée, la page s'affiche par défaut en français, et un lien en bas de page permet d'atteindre la version en anglais.
Le code sur l'infobrol est automatiquement coloré selon la syntaxe, et les différents mots clés sont transformés en liens pour accéder rapidement aux informations.
Vous avez la possibilité de partager vos expériences en proposant vos propres extraits de code en utilisant le bouton "ajouter un commentaire" en bas de page. Si vous visitez simplement l'infobrol, vous avez déjà accès à cette fonction, mais si vous étes membre du brol, vous pouvez en plus utiliser des boutons supplémentaires de mise en forme, dont la coloration automatique de vos extraits de codes.
Vous pouvez modifier vos préférences dans votre profil pour ne plus afficher les interactions avec les réseaux sociaux sur ces pages.
7 mots clés dont 0 définis manuellement (plus d'information...).
Avertissement
Cette page ne possède pas encore de mots clés manuels, ceci est donc un exemple automatique (les niveaux de pertinence sont fictifs, mais les liens sont valables). Pour tester le nuage avec une page qui contient des mots définis manuellement, vous pouvez cliquer ici.Vous pouvez modifier vos préférences dans votre profil pour ne plus afficher le nuage de mots clés.
Recherche (afficher)
Utilisateur (masquer)
Navigation (masquer)
Apparence (afficher)
Stats (afficher)
Citation (masquer)