Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.apache.xerces.readers: Javadoc index of package org.apache.xerces.readers.

Package Samples:



MIME2Java: MIME2Java is a convenience class which handles conversions between MIME charset names and Java encoding names. The supported XML encodings are the intersection of XML-supported code sets and those supported in JDK 1.1. MIME charset names are used on xmlEncoding parameters to methods such as TXDocument#setEncoding and DTD#setEncoding . Java encoding names are used on encoding parameters to methods such as TXDocument#printWithFormat and DTD#printExternal . Common Name Use this name in XML files Name Type Xerces converts to this Java Encoder Name 8 bit Unicode UTF-8 IANA UTF8 ISO Latin 1 ISO-8859-1 ...
XCatalog: This catalog supports the XCatalog proposal draft 0.2 posted to the xml-dev mailing list by John Cowan . XCatalog is an XML representation of the SGML Open TR9401:1997 catalog format. The current proposal supports public identifier maps, system identifier aliases, and public identifier prefix delegates. Refer to the XCatalog DTD for the full specification of this catalog format at . In order to use XCatalogs, you must write the catalog files with the following restrictions: You must follow the XCatalog grammar. You must specify the <!DOCTYPE> line ...
UTF8Reader: This is the primary reader used for UTF-8 encoded byte streams. This reader processes requests from the scanners against the underlying UTF-8 byte stream, avoiding when possible any up-front transcoding. When the StringPool handle interfaces are used, the information in the data stream will be added to the string pool and lazy-evaluated until asked for. We use the SymbolCache to match expected names (element types in end tags) and walk the data structures of that class directly. There is a significant amount of hand-inlining and some blatant voilation of good object oriented programming rules, ...
XMLCatalogHandler: Interface for implementing basic catalog support in the parser. To implement and use a Catalog, implement this interface and install your catalog instance as the EntityResolver in the parser's entity handler. For example: XMLParser parser = new AnyParser(); parser.addCatalogHandler(new MyCatalog()); This default catalog implementation does not provide a method for loading multiple catalogs from various input sources. Instead, it is a convenient base class for other catalog implementations. To create a catalog implementation, simply extend this class and implement the loadCatalog method. Public ...
XMLDeclRecognizer: Abstract base class for encoding recognizers. When we encounter an external entity, including the document entity, and do not know what the encoding of the underlying byte stream is, we need to look at the contents of the stream to find out. We do this by asking a set of "recognizers" to look at the stream data and if the recognizer can understand the encoding it will try to read an XML or text declaration, if present, and construct the appropriate reader for that encoding. The recognizer subclasses will typically use the prescanXMLDeclOrTextDecl() method if the stream looks like it does begin ...
StringReader: Reader for processing internal entity replacement text. This reader processes data contained within strings kept in the string pool. It provides the support for both general and parameter entities. The location support as we are processing the replacement text is somewhat poor and needs to be updated when "nested locations" have been implemented. For efficiency, we return instances of this class to a free list and reuse those instances to process other strings.
CharReader: General purpose character stream reader. This class is used when the input source for the document entity is specified using a character stream, when the input source is specified using a byte stream with an explicit encoding, or when a recognizer scans the encoding decl from the byte stream and chooses to use this reader class for that encoding. For the latter two cases, the byte stream is wrapped in the appropriate InputStreamReader using the desired encoding.
UTF8CharReader: Simple character-based version of a UTF8 reader. This class is not commonly used, but is provided as a much simplified example of the UTF8Reader class that uses the AbstractCharReader to perform all of the reader functions except for filling each buffer of the character data when needed (fillCurrentChunk). We read the input data from an InputStream and perform end-of-line normalization as we process that data.
UCSReader: Reader for UCS-2 and UCS-4 encodings. This reader is created by the UCSRecognizer class when it decides that the byte stream is encoded in a format supported by this class. This class was intended to be another example of an encoding sensitive reader that could take advantage of the system design to improve performance and reduce resource consumption, but the actual performance tuning remains to be done.
AbstractCharReader: An abstract class for readers that process input data as characters. This is the base class of the CharReader and UTF8CharReader classes. The CharReader classes fills in the "chunks" of data to process from a character stream ( The UTF8CharReader performs its own UTF-8 transcoding to fill in the data from an InputStream.
XMLEntityHandler: This is the interface used for entity management. This interface is typically implemented by the "parser" class to provide entity management services for the scanner classes.
StreamingCharReader: An reader class for applications that need to process input data as it arrives on the stream.
XMLEntityReader: This is the class used by the scanner to process the XML data.
XMLEntityReaderFactory: This is the factory interface used to create readers.
DefaultEntityHandler: Default entity handler implementation.

Home | Contact Us | Privacy Policy | Terms of Service