Home >> All >> org >> apache >> xml >> [ res 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.res: Javadoc index of package org.apache.xml.res.


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.
• XMLErrorResources: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_sv: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_de: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_sk: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_it: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_ru: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_ja: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_ko: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_tr: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_cs: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_hu: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_zh_TW: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_fr: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_zh_CN: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_ca: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )
• XMLErrorResources_pl: Set up error messages. We build a two dimensional array of message keys and message strings. In order to add a new message here, you need to first add a String constant. And you need to enter key, value pair as part of the contents array. You also need to update MAX_CODE for error strings and MAX_WARNING for warnings ( Needed for only information purpose )

Home | Contact Us | Privacy Policy | Terms of Service