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

Quick Search    Search Deep

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


Package Samples:

org.apache.xerces.tree

Classes:

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 ...
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 ...
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 ...
AttributeNode: Node representing an XML attribute. Many views of attributes can be useful, but only the first of these is explicitly supported: Logical View Attributes always hold a string created by expanding character and entity references from source text conforming to the XML specification. If this attribute was declared in a DTD, normalization will often be done to eliminate insignificant whitespace. DTD Validated View If the attribute was declared in a DTD, it will have minimal semantics provided by its declaration, and checked by validating parsers. For example, the logical view may name one (or many) ...
ElementNode: This class represents XML elements in a parse tree, and is often subclassed to add custom behaviors. When an XML Document object is built using an XmlDocumentBuilder instance, simple declarative configuration information may be used to control whether this class, or some specialized subclass (e.g. supporting HTML DOM methods) is used for elements in the resulting tree. As well as defining new methods to provide behaviors which are specific to application frameworks, such as Servlets or Swing, such subclasses may also override methods such as doneParse and appendChild to perform some kinds of processing ...
DtdEventListener: When parsing XML documents, DTD related events are signaled through this interface. Examples include the beginning and end of the DTD, entity declarations, and parts of the <!DOCTYPE...> declaration. This interface supports: SAX 1.0 DtdHandler callbacks, which suffice to interpret element attributes whose values name notations or unparsed entities. DOM Level 1, which additionally requires information about parsed entity declarations, as well as the ability to tell which processing instructions are within the DTD. XML namespaces, which places requirements on names of all entities and notations ...
TreeWalker: This class implements a preorder depth first walk over the tree rooted at a given DOM node. The traversal is "live", and terminates either when that given node is reached when climbing back up, or when a null parent node is reached. It may be restarted via reset() . The way this remains live is to have a "current" node to which the walk is tied. If the tree is modified, that current node will always still be valid ... even if it is no longer connected to the rest of the document, or if it's reconnected at a different location. The behavior of tree modifications is specified by DOM, and the interaction ...
XmlReader: This handles several XML-related tasks that normal java.io Readers don't support, inluding use of IETF standard encoding names and automatic detection of most XML encodings. The former is needed for interoperability; the latter is needed to conform with the XML spec. This class also optimizes reading some common encodings by providing low-overhead unsynchronized Reader support. Note that the autodetection facility should be used only on data streams which have an unknown character encoding. For example, it should never be used on MIME text/xml entities. Note that XML processors are only required ...
DocumentEx: This interface extends the DOM Document model in several useful ways. It supports: Application-specialized element creation and document customization at parse time; Document printing; The URI with which the document is associated; Access to elements by their XML "ID" attributes (when the document was constructed with an appropriate XML parser); Application-level control over the language in which diagnostics are provided (useful for multi-language applications such as servers); Moving nodes between DOM Documents. (DOM Level 1 only talks about nodes that are coupled to a single DOM document.)
ElementFactory: This interface defines a factory which can be used by documents to provide namespace-aware element creation. A variety of implementation techniques are possible for this interface. Among them are compiled-in mappings between element names and classes, mappings defined in configuration files, ones derived from the document as it is parsed, and using namespaces to identify packages to be used with classes whose names correspond to elements. DOM implementations will have constraints on the implementation classes returned by this factory, typically that they be subclasses of their implementation base ...
XmlReadable: This interface is supported by XML documents and elements which wish to interact with DOM construction during parsing of XML documents. The parse context which is provided allows elements to determine the URI of the document in which they are found, for interpreting relative URIs. It also supports providing application level diagnostics for faulty input. When these methods are called, parent context is available for elements so that "inherited" attributes may be queried, as well as other information such as the types of any containing elements.
ParentNode: This adds an implementation of "parent of" relationships to the NodeBase class. It implements operations for maintaining a set of children, providing indexed access to them, and writing them them out as text. The NodeList it implements to describe its children is "live", as required by DOM. That means that indexed accesses by applications must handle cases associated with unstable indices and lengths. Indices should not be stored if they can be invalidated by changes, including changes made by other threads.
ElementEx: This extends the DOM Element interface with features including XML namespace support. An ID attribute may be visible, and applications may request that memory usage be reduced. There is also support for a single strongly associated object, permitting trees of XML objects to be coupled to other frameworks without requiring either subclassing or external tables to manage such associations. Such techniques will be required in some cases, perhaps in conjunction with this userObject .
NodeBase: Base class for DOM parse tree nodes which may appear in XmlDocument nodes. This implements "parented by" and "owning document" relationships. If the parent is not null, this also supports sibling relationships through that parent. Children may be directly accessed through this class, although it is subclasses which implement that access.
CDataNode: Node representing XML CDATA text, which is just like other text except for its delimiters ( <[CDATA[ text ]]> ). CDATA is used to embed markup, program source code, and other kinds of text that use XML markup delimiters ( < and & ) for their own nefarious purposes.
PINode: Node representing an XML processing instruction. Functionality to restore in some other way: As a convenience function, the instruction data may optionally be parsed as element attributes are parsed. There is no requirement to use this particular syntax for instruction data.
ParseContext: This interface is used during parsing of XML content to encapsulate information about the location of the parsing event being reported. It is used to report diagnostics for application level problems that relate to the data which was successfuly parsed, and to resolve relative URIs.
XmlWriteContext: This captures context used when writing XML text, such as state used to "pretty print" output or to identify entities which are defined. Pretty printing is useful when displaying structure in XML documents that need to be read or edited by people (rather than only by machines).
AttributeSet: Class representing an XML attribute list. This couples slightly with the Sun XML parser, in that it optionally uses an extended SAX 1.0 API to see if an attribute was specified in the document or was instead defaulted by attribute processing.
AttributeListEx: This interface extends the SAX AttributeList interface to expose information needed to support DOM Level 1 features used in document editing, and detection of ID attributes which are declared for an element.
TextNode: Node representing XML text. Subclasses should not currently attempt to modify the representation of content, but may add new methods to support more sophisticated access or manipulation of that content.
DataNode: Node representing XML character data, such as text (including CDATA sections and comments). At this time this uses an unsophisticated representation which is not suited for complex editing operations.
XmlNames: This class contains static methods used to determine whether identifiers may appear in certain roles in XML documents. Such methods are used both to parse and to create such documents.

Home | Contact Us | Privacy Policy | Terms of Service