Home >> All >> org >> apache >> xerces >> [ util Javadoc ]

•	org.apache.xerces.utils.regex.* (10)

• org.apache.xerces.util: Javadoc index of package org.apache.xerces.util.


Package Samples:

• org.apache.xerces.utils.regex

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 ...
• 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 ...
• URI: A class to represent a Uniform Resource Identifier (URI). This class is designed to handle the parsing of URIs and provide access to the various components (scheme, host, port, userinfo, path, query string and fragment) that may constitute a URI. Parsing of a URI specification is done according to the URI syntax described in RFC 2396 , and amended by RFC 2732 . Every absolute URI consists of a scheme, followed by a colon (':'), followed by a scheme-specific part. For URIs that follow the "generic URI" syntax, the scheme-specific part begins with two slashes ("//") and may be followed by an authority ...
• URI: A class to represent a Uniform Resource Identifier (URI). This class is designed to handle the parsing of URIs and provide access to the various components (scheme, host, port, userinfo, path, query string and fragment) that may constitute a URI. Parsing of a URI specification is done according to the URI syntax described in RFC 2396 . Every URI consists of a scheme, followed by a colon (':'), followed by a scheme-specific part. For URIs that follow the "generic URI" syntax, the scheme- specific part begins with two slashes ("//") and may be followed by an authority segment (comprised of user information, ...
• ChunkyByteArray: This class is used for accessing the data provided by an InputStream. There are two ways in which this class is used. The first occurs when we are prescanning the start of the stream to determine the encoding being used. Since we do not require that the stream be positionable, we wrap it with an instance of this class. The first "chunk" of the file is read and the data may be accessed directly using the byteAt(offset) method. After we have determined the encoding of the byte stream, the instance of this class is passed on to the EntityReader that will process the data for the scanner. At this point, ...
• SecurityManager: This class is a container for parser settings that relate to security, or more specifically, it is intended to be used to prevent denial-of-service attacks from being launched against a system running Xerces. Any component that is aware of a denial-of-service attack that can arise from its processing of a certain kind of document may query its Component Manager for the property (http://apache.org/xml/properties/security-manager) whose value will be an instance of this class. If no value has been set for the property, the component should proceed in the "usual" (spec-compliant) manner. If a value ...
• SymbolTable: This class is a symbol table implementation that guarantees that strings used as identifiers are unique references. Multiple calls to addSymbol will always return the same string reference. The symbol table performs the same task as String.intern() with the following differences: A new string object does not need to be created in order to retrieve a unique reference. Symbols can be added by using a series of characters in a character array. Users of the symbol table can provide their own symbol hashing implementation. For example, a simple string hashing algorithm may fail to produce a balanced ...
• XMLCatalogResolver: The catalog resolver handles the resolution of external identifiers and URI references through XML catalogs. This component supports XML catalogs defined by the OASIS XML Catalogs Specification . It encapsulates the XML Commons resolver. An instance of this class may be registered on the parser as a SAX entity resolver or as an XNI entity resolver by setting the property (http://apache.org/xml/properties/internal/entity-resolver). It is intended that this class may be used standalone to perform catalog resolution outside of a parsing context. It may be shared between several parsers and the application ...
• XMLStringBuffer: XMLString is a structure used to pass character arrays. However, XMLStringBuffer is a buffer in which characters can be appended and extends XMLString so that it can be passed to methods expecting an XMLString object. This is a safe operation because it is assumed that any callee will not modify the contents of the XMLString structure. The contents of the string are managed by the string buffer. As characters are appended, the string buffer will grow as needed. Note: Never set the ch , offset , and length fields directly. These fields are managed by the string buffer. In order to reset the buffer, ...
• XMLChar: This class defines the basic XML character properties. The data in this class can be used to verify that a character is a valid XML character or if the character is a space, name start, or name character. A series of convenience methods are supplied to ease the burden of the developer. Because inlining the checks can improve per character performance, the tables of character properties are public. Using the character as an index into the CHARS array and applying the appropriate mask flag (e.g. MASK_VALID ), yields the same results as calling the convenience methods. There is one exception: check ...
• XML11Char: This class defines the basic properties of characters in XML 1.1. The data in this class can be used to verify that a character is a valid XML 1.1 character or if the character is a space, name start, or name character. A series of convenience methods are supplied to ease the burden of the developer. Using the character as an index into the XML11CHARS array and applying the appropriate mask flag (e.g. MASK_VALID ), yields the same results as calling the convenience methods. There is one exception: check the comments for the isValid method for details.
• XMLAttributesImpl: The XMLAttributesImpl class is an implementation of the XMLAttributes interface which defines a collection of attributes for an element. In the parser, the document source would scan the entire start element and collect the attributes. The attributes are communicated to the document handler in the startElement method. The attributes are read-write so that subsequent stages in the document pipeline can modify the values or change the attributes that are propogated to the next stage.
• ParserConfigurationSettings: This class implements the basic operations for managing parser configuration features and properties. This utility class can be used as a base class for parser configurations or separately to encapsulate a number of parser settings as a component manager. This class can be constructed with a "parent" settings object (in the form of an XMLComponentManager ) that allows parser configuration settings to be "chained" together.
• DOMUtil: Some useful utility methods. This class was modified in Xerces2 with a view to abstracting as much as possible away from the representation of the underlying parsed structure (i.e., the DOM). This was done so that, if Xerces ever adopts an in-memory representation more efficient than the DOM (such as a DTM), we should easily be able to convert our schema parsing to utilize it.
• StringHasher: Algorithm used to hash char arrays (strings). This class was created after it was discovered that parsing some documents was unexpectedly slow due to many different strings hashing to the same 32-bit value using the java.lang.String hash algorithm. The trick seems to be the shift of the top eight bits of the hashcode back down to the bottom to keep them from being rolled out.
• XMLGrammarPoolImpl: Stores grammars in a pool associated to a specific key. This grammar pool implementation stores two types of grammars: those keyed by the root element name, and those keyed by the grammar's target namespace. This is the default implementation of the GrammarPool interface. As we move forward, this will become more function-rich and robust.
• AugmentationsImpl: This class provides an implementation for Augmentations interface. Augmentations interface defines a hashtable of additional data that could be passed along the document pipeline. The information can contain extra arguments or infoset augmentations, for example PSVI. This additional information is identified by a String key.
• Base64: This class provides encode/decode for RFC 2045 Base64 as defined by RFC 2045, N. Freed and N. Borenstein. RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. Reference 1996 Available at: http://www.ietf.org/rfc/rfc2045.txt This class is used by XML Schema binary format validation
• XMLCharacterProperties: A class representing properties of characters according to various W3C recommendations XMLCharacterProperties provides convenience methods for commonly used character tests. For performance reasons, the tables used by the convenience methods are also public, and are directly accessed by performance critical routines.
• CharDataChunk: This class provides the character buffers used by some of the reader classes. The instances of this class are reference counted and placed upon a free list for reallocation when no longer in use so that they are reclaimed faster and with less overhead than using the garbage collector.
• ShadowedSymbolTable: Shadowed symbol table. The table has a reference to the main symbol table and is not allowed to add new symbols to the main symbol table. New symbols are added to the shadow symbol table and are local to the component using this table.
• NamespaceSupport: Namespace support for XML document handlers. This class doesn't perform any error checking and assumes that all strings passed as arguments to methods are unique symbols. The SymbolTable class can be used for this purpose.
• NamespacesScope: NamespacesScope provides a data structure for mapping namespace prefixes to their URI's. The mapping accurately reflects the scoping of namespaces at a particular instant in time.
• SynchronizedSymbolTable: Synchronized symbol table. This class moved into the util package since it's needed by multiple other classes (CachingParserPool, XMLGrammarCachingConfiguration).
• MessageFormatter: This interface provides a generic message formatting mechanism and is useful for producing messages that must be localed and/or formatted with replacement text.

Home | Contact Us | Privacy Policy | Terms of Service