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

Quick Search    Search Deep

Page 1   2  
org.apache.xerces.dom.* (69)org.apache.xerces.dom3.* (30)org.apache.xerces.domx.* (2)
org.apache.xerces.framework.* (8)org.apache.xerces.impl.* (208)org.apache.xerces.jaxp.* (6)
org.apache.xerces.msg.* (6)org.apache.xerces.parsers.* (26)org.apache.xerces.readers.* (19)
org.apache.xerces.tree.* (33)

Package Samples:

org.apache.xerces.dom.events
org.apache.xerces.dom
org.apache.xerces.domx
org.apache.xerces.framework
org.apache.xerces.jaxp
org.apache.xerces.msg
org.apache.xerces.parsers
org.apache.xerces.readers
org.apache.xerces.tree
org.apache.xerces.impl.xs.models
org.apache.xerces.impl.xs.util
org.apache.xerces.impl.xs.identity
org.apache.xerces.impl.xs.opti
org.apache.xerces.impl.xs.traversers
org.apache.xerces.impl.xs
org.apache.xerces.impl.dv.dtd
org.apache.xerces.impl.dv.xs
org.apache.xerces.impl.dv.util
org.apache.xerces.impl.dv
org.apache.xerces.impl.dtd.models

Classes:

RegularExpression: A regular expression matching engine using Non-deterministic Finite Automaton (NFA). This engine does not conform to the POSIX regular expression. How to use A. Standard way RegularExpression re = new RegularExpression( regex ); if (re.matches(text)) { ... } B. Capturing groups RegularExpression re = new RegularExpression( regex ); Match match = new Match(); if (re.matches(text, match)) { ... // You can refer captured texts with methods of the Match class. } Case-insensitive matching RegularExpression re = new RegularExpression( regex , "i"); if (re.matches(text) >= 0) { ...} Options You can specify ...
RegularExpression: A regular expression matching engine using Non-deterministic Finite Automaton (NFA). This engine does not conform to the POSIX regular expression. How to use A. Standard way RegularExpression re = new RegularExpression( regex ); if (re.matches(text)) { ... } B. Capturing groups RegularExpression re = new RegularExpression( regex ); Match match = new Match(); if (re.matches(text, match)) { ... // You can refer captured texts with methods of the Match class. } Case-insensitive matching RegularExpression re = new RegularExpression( regex , "i"); if (re.matches(text) >= 0) { ...} Options You can specify ...
DOMConfiguration: The DOMConfiguration interface represents the configuration of a document and maintains a table of recognized parameters. Using the configuration, it is possible to change Document.normalizeDocument() behavior, such as replacing the CDATASection nodes with Text nodes or specifying the type of the schema that must be used when the validation of the Document is requested. DOMConfiguration objects are also used in [ DOM Level 3 Load and Save ] in the DOMParser and DOMSerializer interfaces. The parameter names used by the DOMConfiguration object are defined throughout the DOM Level 3 specifications. ...
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 ...
EncodingMap: EncodingMap is a convenience class which handles conversions between IANA encoding names and Java encoding names, and vice versa. The encoding names used in XML instance documents must be the IANA encoding names specified or one of the aliases for those names which IANA defines. 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 MIME ISO-8859-1 ISO Latin 2 ISO-8859-2 MIME ISO-8859-2 ISO Latin 3 ISO-8859-3 MIME ISO-8859-3 ISO Latin 4 ISO-8859-4 MIME ISO-8859-4 ISO Latin Cyrillic ISO-8859-5 MIME ISO-8859-5 ...
TraverseSchema: Instances of this class get delegated to Traverse the Schema and to populate the Grammar internal representation by instances of Grammar objects. Traverse a Schema Grammar: As of April 07, 2000 the following is the XML Representation of Schemas and Schema components, Chapter 4 of W3C Working Draft. Content: ((include | import | annotation)* , ((simpleType | complexType | element | group | attribute | attributeGroup | notation) , annotation*)+) Content: (annotation? , simpleType?) Content: (annotation? , (simpleType | complexType)? , (unique | key | keyref)*) Content: (annotation? , (((minExclusive ...
MessageCatalog: This class provides support for multi-language string lookup, as needed to localize messages from applications supporting multiple languages at the same time. One class of such applications is network services, such as HTTP servers, which talk to clients who may not be from the same locale as the server. This class supports a form of negotiation for the language used in presenting a message from some package, where both user (client) preferences and application (server) support are accounted for when choosing locales and formatting messages. Each package should have a singleton package-private ...
AttrImpl: Attribute represents an XML-style attribute of an Element. Typically, the allowable values are controlled by its declaration in the Document Type Definition (DTD) governing this kind of document. If the attribute has not been explicitly assigned a value, but has been declared in the DTD, it will exist and have that default. Only if neither the document nor the DTD specifies a value will the Attribute really be considered absent and have no value; in that case, querying the attribute will return null. Attributes may have multiple children that contain their data. (XML allows attributes to contain ...
TypeInfo: The TypeInfo interface represent a type referenced from Element or Attr nodes, specified in the schemas associated with the document. The type is a pair of a namespace URI and name properties, and depends on the document's schema. If the document's schema is an XML DTD [ XML 1.0 ], the values are computed as follows: If this type is referenced from an Attr node, typeNamespace is null and typeName represents the [attribute type] property in the [ XML Information Set ] . If there is no declaration for the attribute, typeName is null . If this type is referenced from an Element node, the typeNamespace ...
XMLContentSpec: ContentSpec really exists to aid the parser classes in implementing access to the grammar. This class is used by the DTD scanner and the validator classes, allowing them to be used separately or together. This "struct" class is used to build content models for validation, where it is more efficient to fetch all of the information for each of these content model "fragments" than to fetch each field one at a time. Since configurations are allowed to have validators without a DTD scanner (i.e. a schema validator) and a DTD scanner without a validator (non-validating processor), this class can be used ...
XMLContentSpec: ContentSpec really exists to aid the parser classes in implementing access to the grammar. This class is used by the DTD scanner and the validator classes, allowing them to be used separately or together. This "struct" class is used to build content models for validation, where it is more efficient to fetch all of the information for each of these content model "fragments" than to fetch each field one at a time. Since configurations are allowed to have validators without a DTD scanner (i.e. a schema validator) and a DTD scanner without a validator (non-validating processor), this class can be used ...
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 http://www.ccil.org/~cowan/XML/XCatalog.html . 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 ...
DeferredEntityReferenceImpl: EntityReference models the XML &entityname; syntax, when used for entities defined by the DOM. Entities hardcoded into XML, such as character entities, should instead have been translated into text by the code which generated the DOM tree. An XML processor has the alternative of fully expanding Entities into the normal document tree. If it does so, no EntityReference nodes will appear. Similarly, non-validating XML processors are not required to read or process entity declarations made in the external subset or declared in external parameter entities. Hence, some applications may not make the replacement ...
EntityReferenceImpl: EntityReference models the XML &entityname; syntax, when used for entities defined by the DOM. Entities hardcoded into XML, such as character entities, should instead have been translated into text by the code which generated the DOM tree. An XML processor has the alternative of fully expanding Entities into the normal document tree. If it does so, no EntityReference nodes will appear. Similarly, non-validating XML processors are not required to read or process entity declarations made in the external subset or declared in external parameter entities. Hence, some applications may not make the replacement ...
Resolver: This entity resolver class provides a number of utilities which can help managment of external parsed entities in XML. These are commonly used to hold markup declarations that are to be used as part of a Document Type Declaration (DTD), or to hold text marked up with XML. Features include: Static factory methods are provided for constructing SAX InputSource objects from Files, URLs, or MIME objects. This eliminates a class of error-prone coding in applications. Character encodings for XML documents are correctly supported: The encodings defined in the RFCs for MIME content types (2046 for general ...
DeepNodeListImpl: This class implements the DOM's NodeList behavior for Element.getElementsByTagName() The DOM describes NodeList as follows: 1) It may represent EITHER nodes scattered through a subtree (when returned by Element.getElementsByTagName), or just the immediate children (when returned by Node.getChildNodes). The latter is easy, but the former (which this class addresses) is more challenging. 2) Its behavior is "live" -- that is, it always reflects the current state of the document tree. To put it another way, the NodeLists obtained before and after a series of insertions and deletions are effectively ...
XMLParserConfiguration: Represents a parser configuration. The parser configuration maintains a table of recognized features and properties, assembles components for the parsing pipeline, and is responsible for initiating parsing of an XML document. By separating the configuration of a parser from the specific parser instance, applications can create new configurations and re-use the existing parser components and external API generators (e.g. the DOMParser and SAXParser). The internals of any specific parser configuration instance are hidden. Therefore, each configuration may implement the parsing mechanism any way necessary. ...
DocumentFragmentImpl: DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfil this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation... and in DOM Level 1, nodes ...
BasicParserConfiguration: A very basic parser configuration. This configuration class can be used as a base class for custom parser configurations. The basic parser configuration creates the symbol table (if not specified at construction time) and manages all of the recognized features and properties. The basic parser configuration does not mandate any particular pipeline configuration or the use of specific components except for the symbol table. If even this is too much for a basic parser configuration, the programmer can create a new configuration class that implements the XMLParserConfiguration interface. Subclasses ...
XmlDocument: This class implements the DOM Document interface, and also provides static factory methods to create document instances. Instances represent the top level of an XML 1.0 document, typically consisting of processing instructions followed by one tree of XML data. These documents may be written out for transfer or storage using a variety of text encodings. The static factory methods do not offer any customization options. in particular, they do not enforce XML Namespaces when parsing, do not offer customizable element factories, and discard certain information which is not intended to be significant ...
SimpleElementFactory: This is a convenience class for creating application-specific elements associated with specified (or default) XML namespaces. It maintains tables mapping element tag names to classes, and uses them as needed to instantiate classes. The string *Element , which is not a legal XML element name, may be used to map otherwise unrecognized tags to a particular class. If this factory is not configured, then all mappings are to the ElementNode class. Erroneous mappings are fatal errors. A suggested XML syntax for recording these bindings, which may in the future be explicitly supported, is: <bindings ...
XmlDocumentBuilder: This class is a SAX DocumentHandler which converts a stream of parse events into an in-memory DOM document. After each Parser.parse() invocation returns, a resulting DOM Document may be accessed via the getDocument method. The parser and its builder should be used together; the builder may be used with only one parser at a time. This builder optionally does XML namespace processing, reporting conformance problems as recoverable errors using the parser's error handler. To customize the document, a powerful technique involves using an element factory specifying what element tags (from a given XML ...
NodeImpl: NodeImpl provides the basic structure of a DOM tree. It is never used directly, but instead is subclassed to add type and data information, and additional methods, appropriate to each node of the tree. Only its subclasses should be instantiated -- and those, with the exception of Document itself, only through a specific Document's factory methods. The Node interface provides shared behaviors such as siblings and children, both for consistancy and so that the most common tree operations may be performed without constantly having to downcast to specific node types. When there is no obvious mapping ...
ParentNode: ParentNode inherits from ChildNode and adds the capability of having child nodes. Not every node in the DOM can have children, so only nodes that can should inherit from this class and pay the price for it. ParentNode, just like NodeImpl, also implements NodeList, so it can return itself in response to the getChildNodes() query. This eliminiates the need for a separate ChildNodeList object. Note that this is an IMPLEMENTATION DETAIL; applications should _never_ assume that this identity exists. On the other hand, subclasses may need to override this, in case of conflicting names. This is the case ...
DOMExceptionImpl: DOMExceptions are thrown when one of the DOM implementation classes discovers an error condition. The architecture is defined in terms of the ExceptionCode, but in the standard Java API this has been extended so the exception may also carry a text string. Standard exception codes are: INDEX_SIZE_ERR: index or size is negative, or greater than the allowed value. WSTRING_SIZE_ERR: the specified range of text does not fit into the string representation used in this implementation. Only arises in implementations whose strings have a maximum-size limit. The DOM provides workarounds to support those ...

Home | Contact Us | Privacy Policy | Terms of Service