| Home >> All >> org >> apache >> tomcat >> [ util Javadoc ] |
Page 1 2
• org.apache.tomcat.util: Javadoc index of package org.apache.tomcat.util.
Package Samples:
• org.apache.tomcat.util.pattern: Utilities used by the rest of com.sun.web.*
• org.apache.tomcat.util.buf
• org.apache.tomcat.util.collections
• org.apache.tomcat.util.compat
• org.apache.tomcat.util.digester
• org.apache.tomcat.util.http.mapper
• org.apache.tomcat.util.http
• org.apache.tomcat.util.log
• org.apache.tomcat.util.net.jsse
• org.apache.tomcat.util.net.puretls
• org.apache.tomcat.util.net
• org.apache.tomcat.util.res
• org.apache.tomcat.util.loader
Classes:
• CallMethodRule: Rule implementation that calls a method on an object on the stack (normally the top/parent object), passing arguments collected from subsequent CallParamRule rules or from the body of this element. By using CallMethodRule(String methodName) 55 a method call can be made to a method which accepts no arguments. Incompatible method parameter types are converted using org.apache.commons.beanutils.ConvertUtils . This rule now uses org.apache.commons.beanutils.MethodUtils#invokeMethod by default. This increases the kinds of methods successfully and allows primitives to be matched by passing in wrapper ...
• NodeCreateRule: A rule implementation that creates a DOM Node containing the XML at the element that matched the rule. Two concrete types of nodes can be created by this rule: the default is to create an Element node. The created element will correspond to the element that matched the rule, containing all XML content underneath that element. alternatively, this rule can create nodes of type DocumentFragment , which will contain only the XML content under the element the rule was trigged on. The created node will be normalized, meaning it will not contain text nodes that only contain white space characters. The ...
• Loader: Boostrap loader for Catalina or other java apps. This application constructs a class loader for use in loading the Catalina internal classes (by accumulating all of the JAR files found in the "server" directory under "catalina.home"), and starts the regular execution of the container. The purpose of this roundabout approach is to keep the Catalina internal classes (and any other classes they depend on, such as an XML parser) out of the system class path and therefore not visible to application level classes. Merged with CatalinaProperties: Load a properties file describing the modules and startup ...
• AbstractRulesImpl: AbstractRuleImpl provides basic services for Rules implementations. Extending this class should make it easier to create a Rules implementation. AbstractRuleImpl manages the Digester and namespaceUri properties. If the subclass overrides registerRule(java.lang.String, org.apache.tomcat.util.digester.Rule) 55 (rather than add(java.lang.String, org.apache.tomcat.util.digester.Rule) 55 ), then the Digester and namespaceURI of the Rule will be set correctly before it is passed to registerRule . The subclass can then perform whatever it needs to do to register the rule.
• ServerSocketFactory: This class creates server sockets. It may be subclassed by other factories, which create particular types of server sockets. This provides a general framework for the addition of public socket-level functionality. It it is the server side analogue of a socket factory, and similarly provides a way to capture a variety of policies related to the sockets being constructed. Like socket factories, Server Socket factory instances have two categories of methods. First are methods used to create sockets. Second are methods which set properties used in the production of sockets, such as networking options. ...
• WriteConvertor: Special writer class, where close() is overritten. The default implementation would set byteOutputter to null, and the writter can't be recycled. Note that the flush method will empty the internal buffers _and_ call flush on the output stream - that's why we use an intermediary output stream that overrides flush(). The idea is to have full control: flushing the char->byte converter should be independent of flushing the OutputStream. When a WriteConverter is created, it'll allocate one or 2 byte buffers, with a 8k size that can't be changed ( at least in JDK1.1 -> 1.4 ). It would also allocate a ...
• CallParamRule: Rule implementation that saves a parameter for use by a surrounding CallMethodRule . This parameter may be: from an attribute of the current element See CallParamRule(int paramIndex, String attributeName) 55 from current the element body See CallParamRule(int paramIndex) 55 from the top object on the stack. See CallParamRule(int paramIndex, boolean fromStack) 55 the current path being processed (separate Rule ). See PathCallParamRule
• MimeHeaders: This class is used to contain standard internet message headers, used for SMTP (RFC822) and HTTP (RFC2068) messages as well as for MIME (RFC 2045) applications such as transferring typed data and grouping related items in multipart message bodies. Message headers, as specified in RFC822, include a field name and a field body. Order has no semantic significance, and several fields with the same name may exist. However, most fields do not (and should not) exist more than once in a header. Many kinds of field body must conform to a specified syntax, including the standard parenthesized comment syntax. ...
• SimpleHashtable: This class implements a special purpose hashtable. It works like a normal java.util.Hashtable except that: Keys to "get" are strings which are known to be interned, so that "==" is used instead of "String.equals". (Interning could be document-relative instead of global.) It's not synchronized, since it's to be used only by one thread at a time. The keys () enumerator allocates no memory, with live updates to the data disallowed. It's got fewer bells and whistles: fixed threshold and load factor, no JDK 1.2 collection support, only keys can be enumerated, things can't be removed, simpler inheritance; ...
• ArrayStack: Imported copy of the ArrayStack class from Commons Collections, which was the only direct dependency from Digester. WARNNG - This class is public solely to allow it to be used from subpackages of org.apache.commons.digester . It should not be considered part of the public API of Commons Digester. If you want to use such a class yourself, you should use the one from Commons Collections directly. An implementation of the java.util.Stack API that is based on an ArrayList instead of a Vector , so it is not synchronized to protect against multi-threaded access. The implementation is therefore operates ...
• NetworkClassLoader: The correct name for this class should be URLClassLoader. But there is already a class by that name in JDK1.2. I have had quite a few problems with URLClassLoader in past, so I ended up writing this ClassLoader. I found that the Java 2's URLClassLoader, does not close the Jar file once opened. It is a pretty good optimization step, but if you modify the class in the jar file, it does not pick it up. Some operating systems may not let you modify the jar file while it is still open. IMHO, it does make sense to close the jar file after you are done reading the class data. But this approach may not ...
• Digester: A Digester processes an XML input stream by matching a series of element nesting patterns to execute Rules that have been added prior to the start of parsing. This package was inspired by the XmlMapper class that was part of Tomcat 3.0 and 3.1, but is organized somewhat differently. See the Digester Developer Guide for more information. IMPLEMENTATION NOTE - A single Digester instance may only be used within the context of a single thread at a time, and a call to parse() must be completed before another can be initiated even from the same thread. IMPLEMENTATION NOTE - A bug in Xerces 2.0.2 prevents ...
• URL: URL is designed to provide public APIs for parsing and synthesizing Uniform Resource Locators as similar as possible to the APIs of java.net.URL , but without the ability to open a stream or connection. One of the consequences of this is that you can construct URLs for protocols for which a URLStreamHandler is not available (such as an "https" URL when JSSE is not installed). WARNING - This class assumes that the string representation of a URL conforms to the spec argument as described in RFC 2396 "Uniform Resource Identifiers: Generic Syntax": <scheme>//<authority><path>?<query>#<fragment> ...
• ByteChunk: This class is used to represent a chunk of bytes, and utilities to manipulate byte[]. The buffer can be modified and used for both input and output. There are 2 modes: The chunk can be associated with a sink - ByteInputChannel or ByteOutputChannel, which will be used when the buffer is empty ( on input ) or filled ( on output ). For output, it can also grow. This operating mode is selected by calling setLimit() or allocate(initial, limit) with limit != -1. Various search and append method are defined - similar with String and StringBuffer, but operating on bytes. This is important because it allows ...
• ObjectParamRule: Rule implementation that saves a parameter for use by a surrounding CallMethodRule . This parameter may be: an arbitrary Object defined programatically, assigned when the element pattern associated with the Rule is matched See ObjectParamRule(int paramIndex, Object param) 55 an arbitrary Object defined programatically, assigned if the element pattern AND specified attribute name are matched See ObjectParamRule(int paramIndex, String attributeName, Object param) 55
• RuleSet: Public interface defining a shorthand means of configuring a complete set of related Rule definitions, possibly associated with a particular namespace URI, in one operation. To use an instance of a class that imlements this interface: Create a concrete implementation of this interface. Optionally, you can configure a RuleSet to be relevant only for a particular namespace URI by configuring the value to be returned by getNamespaceURI() . As you are configuring your Digester instance, call digester.addRuleSet() and pass the RuleSet instance. Digester will call the addRuleInstances() method of your ...
• WithDefaultsRulesWrapper: Rules Decorator that returns default rules when no matches are returned by the wrapped implementation. This allows default Rule instances to be added to any existing Rules implementation. These default Rule instances will be returned for any match for which the wrapped implementation does not return any matches. For example, Rule alpha; ... WithDefaultsRulesWrapper rules = new WithDefaultsRulesWrapper(new BaseRules()); rules.addDefault(alpha); ... digester.setRules(rules); ... when a pattern does not match any other rule, then rule alpha will be called. WithDefaultsRulesWrapper follows the Decorator ...
• ObjectCreationFactory: Interface for use with FactoryCreateRule . The rule calls createObject(org.xml.sax.Attributes) 55 to create an object to be pushed onto the Digester stack whenever it is matched. AbstractObjectCreationFactory is an abstract implementation suitable for creating anonymous ObjectCreationFactory implementations.
• RulesBase: Default implementation of the Rules interface that supports the standard rule matching behavior. This class can also be used as a base class for specialized Rules implementations. The matching policies implemented by this class support two different types of pattern matching rules: Exact Match - A pattern "a/b/c" exactly matches a <c> element, nested inside a <b> element, which is nested inside an <a> element. Tail Match - A pattern "*/a/b" matches a <b> element, nested inside an <a> element, no matter how deeply the pair is nested.
• StringManager: An internationalization / localization helper class which reduces the bother of handling ResourceBundles and takes care of the common cases of message formating which otherwise require the creation of Object arrays and such. The StringManager operates on a package basis. One StringManager per package can be created and accessed via the getManager method call. The StringManager will look for a ResourceBundle named by the package name given plus the suffix of "LocalStrings". In practice, this means that the localized information will be contained in a LocalStrings.properties file located in the package ...
• StringManager: An internationalization / localization helper class which reduces the bother of handling ResourceBundles and takes care of the common cases of message formating which otherwise require the creation of Object arrays and such. The StringManager operates on a package basis. One StringManager per package can be created and accessed via the getManager method call. The StringManager will look for a ResourceBundle named by the package name given plus the suffix of "LocalStrings". In practice, this means that the localized information will be contained in a LocalStrings.properties file located in the package ...
• MimeHeaders: Memory-efficient repository for Mime Headers. When the object is recycled, it will keep the allocated headers[] and all the MimeHeaderField - no GC is generated. For input headers it is possible to use the MessageByte for Fileds - so no GC will be generated. The only garbage is generated when using the String for header names/values - this can't be avoided when the servlet calls header methods, but is easy to avoid inside tomcat. The goal is to use _only_ MessageByte-based Fields, and reduce to 0 the memory overhead of tomcat. TODO: XXX one-buffer parsing - for http ( other protocols don't need ...
• SetPropertiesRule: Rule implementation that sets properties on the object at the top of the stack, based on attributes with corresponding names. This rule supports custom mapping of attribute names to property names. The default mapping for particular attributes can be overridden by using SetPropertiesRule(String[] attributeNames, String[] propertyNames) 55 . This allows attributes to be mapped to properties with different names. Certain attributes can also be marked to be ignored.
• FactoryCreateRule: Rule implementation that uses an ObjectCreationFactory to create a new object which it pushes onto the object stack. When the element is complete, the object will be popped. This rule is intended in situations where the element's attributes are needed before the object can be created. A common senario is for the ObjectCreationFactory implementation to use the attributes as parameters in a call to either a factory method or to a non-empty constructor.
• Repository: A group of modules and libraries. Modules can have one or more jars and class dirs. Classloaders are created from modules when the module is started are be disposed when the module is stopped. The module will delegate to the associated repository in addition to the normal delegation rules. The repository will search on all sibling modules. This mechanism is defined in the MLetClassLoader and is also used by JBoss and few other servers. TODO: explain more ( or point to the right jboss/mlet pages ) TODO: explain how this can be used for webapps to support better partitioning
| Home | Contact Us | Privacy Policy | Terms of Service |