| Home >> All >> org >> apache >> xml >> [ resolver Javadoc ] |
| • | org.apache.xml.resolver.apps.* (4) | • | org.apache.xml.resolver.helpers.* (4) |
| • | org.apache.xml.resolver.readers.* (11) | • | org.apache.xml.resolver.tools.* (4) |
• org.apache.xml.resolver: Javadoc index of package org.apache.xml.resolver.
Package Samples:
• org.apache.xml.resolver.tools: Apache XML Commons Resolver package.
• org.apache.xml.resolver.apps
• org.apache.xml.resolver.helpers
• org.apache.xml.resolver.readers
Classes:
• Catalog: Represents OASIS Open Catalog files. This class implements the semantics of OASIS Open Catalog files (defined by OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401) ). The primary purpose of the Catalog is to associate resources in the document with local system identifiers. Some entities (document types, XML entities, and notations) have names and all of them can have either public or system identifiers or both. (In XML, only a notation can have a public identifier without a system identifier, but the methods implemented in this class obey the Catalog semantics from the SGML days when ...
• CatalogManager: CatalogManager provides an interface to the catalog properties. Properties can come from two places: from system properties or from a CatalogManager.properties file. This class provides a transparent interface to both, with system properties preferred over property file values. The following table summarizes the properties: System Property CatalogManager.properties Property Description xml.catalog.ignoreMissing   If true, a missing CatalogManager.properties file or missing properties within that file will not generate warning messages. See also the ignoreMissingProperties method. xml.catalog.files ...
• xread: A simple command-line XML parsing application. This class implements a simple command-line XML Parser. It's just a little wrapper around the JAXP XMLReader with support for catalogs. Usage: xread [options] document.xml Where: -c catalogfile Load a particular catalog file. -w Perform a well-formed parse, not a validating parse. -v (the default) Perform a validating parse. -n Perform a namespace-ignorant parse. -N (the default) Perform a namespace-aware parse. -d integer Set the debug level. Warnings are shown if the debug level is > 2. -E integer Set the maximum number of errors to display. The ...
• xparse: A simple command-line XML parsing application. This class implements a simple command-line XML Parser. It's just a little wrapper around the JAXP Parser with support for catalogs. Usage: xparse [options] document.xml Where: -c catalogfile Load a particular catalog file. -w Perform a well-formed parse, not a validating parse. -v (the default) Perform a validating parse. -n Perform a namespace-ignorant parse. -N (the default) Perform a namespace-aware parse. -d integer Set the debug level. Warnings are shown if the debug level is > 2. -E integer Set the maximum number of errors to display. The ...
• resolver: A simple command-line resolver. This class implements a simple command-line resolver. It takes some parameters and passes them through the resolver, printing the result. Usage: resolver [options] keyword Where options are: -c catalogfile Load a particular catalog file. -n name Sets the name. -p publicId Sets the public identifier. -s systemId Sets the system identifier. -a Absolute system URI. -u uri Sets the URI. -d integer Set the debug level. And keyword is one of: doctype, document, entity, notation, public, system, or uri. The process ends with error-level 1, if there errors.
• DOMCatalogReader: A DOM-based CatalogReader. This class is used to read XML Catalogs using the DOM. This reader has an advantage over the SAX-based reader that it can analyze the DOM tree rather than simply a series of SAX events. It has the disadvantage that it requires all of the code necessary to build and walk a DOM tree. Since the choice of CatalogReaders (in the InputStream case) can only be made on the basis of MIME type, the following problem occurs: only one CatalogReader can exist for all XML mime types. In order to get around this problem, the DOMCatalogReader relies on a set of external CatalogParsers ...
• SAXCatalogReader: A SAX-based CatalogReader. This class is used to read XML Catalogs using the SAX. This reader has an advantage over the DOM-based reader in that it functions on the stream of SAX events. It has the disadvantage that it cannot look around in the tree. Since the choice of CatalogReaders (in the InputStream case) can only be made on the basis of MIME type, the following problem occurs: only one CatalogReader can exist for all XML mime types. In order to get around this problem, the SAXCatalogReader relies on a set of external CatalogParsers to actually build the catalog. The selection of CatalogParsers ...
• CatalogEntry: Represents a Catalog entry. Instances of this class represent individual entries in a Catalog. Each catalog entry has a unique name and is associated with an arbitrary number of arguments (all strings). For example, the TR9401 catalog entry "PUBLIC" has two arguments, a public identifier and a system identifier. Each entry has a unique numeric type, assigned automatically when the entry type is created. The number and type of catalog entries is maintained statically . Catalog classes, or their subclasses, can add new entry types, but all Catalog objects share the same global pool of types. Initially ...
• BootstrapResolver: A simple bootstrapping resolver. This class is used as the entity resolver when reading XML Catalogs. It searches for the OASIS XML Catalog DTD, Relax NG Grammar and W3C XML Schema as resources (e.g., in the resolver jar file). If you have your own DTDs or schemas, you can extend this class and set the BootstrapResolver in your CatalogManager.
• TR9401CatalogReader: Parses OASIS Open Catalog files. This class reads OASIS Open Catalog files, returning a stream of tokens. This code interrogates the following non-standard system properties: xml.catalog.debug Sets the debug level. A value of 0 is assumed if the property is not set or is not a number.
• CatalogResolver: A SAX EntityResolver/JAXP URIResolver that uses catalogs. This class implements both a SAX EntityResolver and a JAXP URIResolver. This resolver understands OASIS TR9401 catalogs, XCatalogs, and the current working draft of the OASIS Entity Resolution Technical Committee specification.
• Debug: Static debugging/messaging class for Catalogs. This class defines a set of static methods that can be called to produce debugging messages. Messages have an associated "debug level" and messages below the current setting are not displayed.
• CatalogReader: The CatalogReader interface. The Catalog class requires that classes implement this interface in order to be used to read catalogs. Examples of CatalogReaders include the TextCatalogReader, the SAXCatalogReader, and the DOMCatalogReader.
• ResolvingXMLFilter: A SAX XMLFilter that performs catalog-based entity resolution. This class implements a SAX XMLFilter that performs entity resolution using the CatalogResolver. The actual, underlying parser is obtained from a SAXParserFactory.
• ResolvingXMLReader: A SAX XMLReader that performs catalog-based entity resolution. This class implements a SAX XMLReader that performs entity resolution using the CatalogResolver. The actual, underlying parser is obtained from a SAXParserFactory.
• ResolvingParser: A SAX Parser that performs catalog-based entity resolution. This class implements a SAX Parser that performs entity resolution using the CatalogResolver. The actual, underlying parser is obtained from a SAXParserFactory.
• Version: Administrative class to keep track of the version number of xml-commons external sources releases. See xml-commons/java/resolver.xml for filtering on 1.0, etc.
• Namespaces: Static Namespace query methods. This class defines a set of static methods that can be called to analyze the namespace properties of DOM nodes.
• PublicId: Static methods for dealing with public identifiers. This class defines a set of static methods that can be called to handle public identifiers.
• DOMCatalogParser: The DOMCatalogParser interface. This interface must be implemented in order for a class to participate as a parser for the DOMCatalogReader.
• SAXCatalogParser: The SAXCatalogParser interface. This interface must be implemented in order for a class to participate as a parser for the SAXCatalogReader.
• SAXParserHandler: An entity-resolving DefaultHandler. This class provides a SAXParser DefaultHandler that performs entity resolution.
• Resolver: An extension to OASIS Open Catalog files, this class supports suffix-based matching and an external RFC2483 resolver.
• XCatalogReader: Parse "xcatalog" XML Catalog files, this is the XML Catalog format developed by John Cowan and supported by Apache.
• CatalogException: Signal Catalog exception. This exception is thrown if an error occurs loading a catalog file.
| Home | Contact Us | Privacy Policy | Terms of Service |