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

Quick Search    Search Deep

org.enhydra.httpServerTest.* (18)org.enhydra.i18n.* (1)org.enhydra.kelp.* (144)
org.enhydra.servlet.* (87)org.enhydra.tool.* (68)org.enhydra.wireless.* (77)
org.enhydra.xml.* (214)

org.enhydra: Javadoc index of package org.enhydra.

Package Samples:

org.enhydra.tool.codegen.en3app: This package contains the core classes and interfaces that make up the CodeGen framework.  
org.enhydra.wireless.wml.dom: Wireless Markup Language (WML) support.  


XMLCContext: Class to facility the use of XMLC in a HTTP servlet. This object contains a XMLC factory to create instances of XMLC document classes and methods to output documents. An instance of this object is associated with the ServletContext object for an application (one per WebApp). The object is created on first use by ( getContext 55 . It provides a factory for creating XMLC document class with optional automatic reloading of out of date classes or recompilation and reloading of classes out-of-date relative to a source file. Also provided are methods to output a XMLC document as a HTTP response, with ...
LazyDocument: A DOM Document that supports lazy instantiation of a template DOM. Nodes in the instance DOM are created as accessed. This can be either by traversing the tree or by direct access to a node by id number. Instantiation of nodes in the middle of the virtual tree is support. Thus a node can exist without a parent being expanded. This is used by XMLC, were the dynamic nodes tend to be towards the leaves of the tree. Instances contain a reference to a DOM that is a shared template for the document. Each node in the template is assigned an integer node id that be used to index tables to directly look ...
MultiServerFilter: This is the base class for filters specified by the administrator in the MultiServer config file. Any filter specified in the MultiServer config file must have two propeties: it must implement the TransactionFilter interface, and it must have a constructor that takes a string and a KeywordValueTable. This abstract class provides these for you, which is why it is recommended that you extend this class if you need to write your own filter for the MultiServer. However, it is possible that a filter absolutly must extend some other class (for example, the RMI connection method can not extend StandardConnectionMethod ...
ConnectionMethod: A ConnectionMethod is how requests get into the server from the outside world. This interface defines the API an object must implement in order to be administered by the server. Each ConnectionMethod must maintain an ordered list of "channels". Each channel has an ID (a String), used to identify and refer to the channel. See addChannel() , below. Each channel can be enabled or disabled. When disabled, connections must be refused, and not passed on to any servlets. When enabled, connections are allowed through to the destination servlet. Each channel also contains an ordered list of TransactionFilters, ...
ServletContainer: Handles requests for Servlets. Multiple connection methods may be routed to one Servlet, or one connection method may direct requests to multiple Servlets (based on URL). Servlets or Enhydra applications (which are a special kind of servlet) or Servlet 2.2 Web applications may be served. This class uses a ServletManager to hold a set of Servlets, a ConnectionMethodManager to hold a set of ConnectionMethods, and a FilterManager to hold a set of Filters. These are available to other classes (for example the admin application). At startup time a configuration file is read, and it describes what ConnectionMethods ...
HttpResponseObject: This class is the data structure that is shared between the client and server tests. The life cycle of this class begins when a client thread's run() method is invoked. The first step in each of the SingleUserGetRequestThread and SingleUserPostRequestThread is to initialize a golden response object of this type from the thread's supplied configuration data. On success of this initialization, each of these threads construct an HTTP request also based on its configuration data. The request is sent to the server which then generates a new object of this type populated with all the request information ...
LazyHTMLDocument: Implements an HTML document. Provides access to the top level element in the document, its body and title. Several methods create new nodes of all basic types (comment, text, element, etc.). These methods create new nodes but do not place them in the document tree. The nodes may be placed in the document tree using Node.appendChild(org.w3c.dom.Node) > Node.appendChild(org.w3c.dom.Node) 55 or Node.insertBefore(org.w3c.dom.Node, org.w3c.dom.Node) > Node.insertBefore(org.w3c.dom.Node, org.w3c.dom.Node) 55 , or they may be placed in some other document tree. Note: <FRAMESET> documents are not ...
DebugManager: Servlet debug manager for monitoring servlet I/O. An instance of this object monitors a single servlet instance. A fixed-sized queue of servlet transaction records is maintained. As a transaction is completed by the servlet, a record is added to the end of the queue. If the queue has reached its maximum size, an element is removed from the head of the queue. Applications wishing to monitor servlet transactions registers with this object and is called when objects are added or removed from the queue. Calling on removal is necessary as one of the main goals of this class is to support presentations ...
LazyNode: Interface use to define Lazy DOM methods that apply to every node. In addition to these methods, each node must: Supply a getTemplateXXX for the specific node type. There are two basic interfaces for implementing LazyDOM nodes: LazyNode and LazyParent, with LazyParent extended LazyNode. They have the following properties: Only LazyParent nodes can contain other nodes. Only LazyParent nodes can exist with out their parent being expanded. All children of a LazyParent are expanded if one of the children is expanded. If a LazyNode that is not a LazyParent is expanded, its siblings are expanded. If ...
ResManager: Some helper functions for handeling i18n issues. One instance of this class should be created for each resource bundle. The ResManager is created by a call to getResourceManager() the parameter is the name of the package that contails the Res class. e.g. ResManager rez = getResourceBundle("org.enhydra.mypackagename"); To use the ResManager make a call to any of the format() methods. In the default resource bundle the key is the same as the value. So to display "I am 2 years old" call rez.format("I am {0} years old",2); If the string "I am {0} years old" is in the bundle the value is returned. If ...
EnhydraDirectorBufferedOutputStream: Extension of BufferedOutputStream to allow "reset" of the buffer. A servlet container's ServletResponse object should not go into the "committed" (data sent) state until the headers have actually been sent over the wire. This allows a servlet to specify a large buffer size and be able to reset or change headers well after the first byte of data has been written to the ServletOutputStream . This class has a reset() that, after checking for committed state of the connection, discards any buffered data and self destructs, dropping any reference to its internally held output stream. Once reset() has ...
XMLCDomFactory: Interface for a factory class that can create DocumentType and Document objects. It also provides document-type specific functions. This is used in implementing subclassed DOMs. Classes implementing this must: Provide a constructor that takes no arguments. Be thread-safe (reentrant is preferred). When a DTD-specific DOM is created, an class implementing this interface must be supplied to XMLC. This would normally be created by extending the XMLCDomDefaultFactory class. This class is designed to be build using a DOMImplementation object. However, since the DOM doesn't specify how DOMImplementation ...
Filter: This replaces the BasicTransactionFilter. Also note that the BasicTransactionServlet is no longer used and that it is functionally replaced by implementing the org.apache.tomcat.core.LifecycleInterceptor and org.apache.tomcat.core.ServiceInterceptor. There is no interface defined for this, since this is a temporary halfway point between the old Enhydra TransactionFilter and the future Tomcat Interceptors. Extend this class to create a filter with additional attributes. The object model is not currently very clean because we need to bridge between the Interceptor model of Tomcat for service(), init(), ...
ServletManager: This class loads Servlet classes, creates instances of Servlets, caches the Servlets, and returns pointers to them. The Servlets are refered to by an identifer string (a symbolic name). First Servlets are registered via add() . Then they are started via start() . Then they are available for use via get() . The ServletManager will call init() on the Servlet. It will also call destoroy() . Other classes which use Servlets returned by get() must not call these two methods. When get() returns a Servlet, it is ready to accept service() calls.
DOMBuilderGenerator: Class to generate code to build the document tree using only the W3C DOM interface. The document building code is generated in several functions to avoid the JVM limit on maximum method size. Since it is not possible to determine the amount of bytecode generate, a metic is defined called create-cost . A unit of create-cost is approximately the cost to create a node and append it to it's parent. The limit on create-cost is determined experimentally. The following methods can be overridden to provide DOM implementation-specific code generation: genNodeCreate - Generates code to create a node.
BasicTestApp: This is the basic application class object for the http server test. This class is very limited in its functionality and simply provides static references to a temporary directory location, setable through the appication configuration file, and a counter. The temorary directory is used for caching of files that are uploaded. The counter is used to ensure that each thread of this application, handling uploaded files, will create a unique sub-directory, under the specified temporary directory, to write to. This allows each thread to only account for uploaded files that occured on the current request ...
StandardConnectionMethod: This is a sample implementation of a ConnectionMethod. It is an abstract class because this class does not actually recieve or generate requests. It does do all the channel managment. Implementations of ConnectionMethod should extend this object, unless there is a specific reason not to. Classes that extend this class will need to implement the getChannelURL() and channelURLIsValid() functions. They will also need to ensure that they contain a thread that is started in the constructor or (prefered) initialize() , and stopped in destroy() .
MkEncodingsTable: Generate a file contain character encodings by parsing the IANA Charset Registry, obtained from: This is a development-time tool, with special hacks to make up for various java encoding names not in the table. The resulting file has the format: name bits mime-name alias1 alias2 ... Where bits is 7, 8 or 16 and mime-name can be "null" if there is none defined. This file will be converted to XML in a future release.
BuildMethodMappings: Class to calculate which elements are to have build methods created for them based on trying to optimize the amount of code (create-cost) in each build methods without overflowing the maximum create-cost. The advantage of this object determining where build methods are created in a seperate traversal from creating the build methods is that the determination is best down from the bottom up, which creating the methods is done top-down. The seperation also keeps the code cleaner and easier to understand. The cost is building an intermediate table.
ConnectionMethodManager: This class maintains a set of ConnectionMethods. Each ConnectionMethod is associated with an identification string (symbolic name). This ID string is used to retrieve a ConnectionMethod. This class does not monitor the creation of ConnectionMethods. If you create one, you are responsible for adding it. These public methods are the only things that modify the set of ConnectionMethods managed by this class. (Note that this is different than the ServletManager, which is responsible for creating the Servlets it manages.)
DOMTraversal: Class that traverse a DOM tree or subtree, calling handler methods for each node. It is up to the handler methods to make a decision on processing child and element nodes by explictly calling the methods to continue the traversal. This is gives the handler more control and actually kept the code simpler for both this class and the client. While DOM traversal is straight-forward, traversing the LazyDOM while avoiding expansion made things tricker. This class, and the derived class for the LazyDOM, handles these special cases.
LazyHTMLElement: Implements an HTML-specific element, an org.w3c.dom.Element that will only appear inside HTML documents. This element extends org.apache.xerces.dom.ElementImpl by adding methods for directly manipulating HTML-specific attributes. All HTML elements gain access to the id , title , lang , dir and class attributes. Other elements add their own specific attributes.
DocTypeBuilder: Class for building a DOM DocumentType. Used by XMLC parsers to build a document DOM. Since the DOM level 1 does not address storing all of the information from the DOCTYPE and DTDs required by XMLC, routine are provided to add this information. Only a subset of the information is actually saved. The internal subset is needed to reproduce the DOCTYPE declaration in the compiled document. The attribute declarations from the external subset are needed to build the table of ID attributes used to generate access methods.
DOMAccess: Method to support accessing the LazyDOM without expanding it. This works both with standard DOMs and LazyDOMs, supporting the development of code that works with either DOM. Most methods come in two flavors, static ones that take the instance document as an argument, an instance methods that use a document contained in an instance of this object. Great care should be used if the return nodes are to be modified, as read-only template nodes maybe returned. These methods also operate on any W3C DOM.
EnhydraDirectorConnectionMethod: The Enhydra connection method. Receives and handles requests using the Enhydra Protocol. The protocol is loosely based on the proposed Apache JServ 2.1 protocol, which uses a packet transmission scheme to allow a more rich set of communcation features between web servers and Enhydra. These features include: Round robin load balancing. Persistent connections. Connection Pools. Callbacks to the front-end web server.

Home | Contact Us | Privacy Policy | Terms of Service