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

Quick Search    Search Deep

org.mortbay.ftp.* (9)org.mortbay.html.* (31)org.mortbay.http.* (81)
org.mortbay.j2ee.* (44)org.mortbay.jaas.* (12)org.mortbay.jetty.* (45)
org.mortbay.jndi.* (8)org.mortbay.loadbalancer.* (7)org.mortbay.servlet.* (12)
org.mortbay.start.* (4)org.mortbay.stop.* (1)org.mortbay.util.* (72)
org.mortbay.webapps.* (3)org.mortbay.xml.* (5)

Package Samples:

org.mortbay.html
org.mortbay.http.ajp
org.mortbay.http.ajp.jmx
org.mortbay.http
org.mortbay.http.handler
org.mortbay.http.jmx
org.mortbay.j2ee
org.mortbay.j2ee.session
org.mortbay.j2ee.session.ejb
org.mortbay.jetty.jmx
org.mortbay.jetty
org.mortbay.jetty.servlet
org.mortbay.jetty.servlet.jmx
org.mortbay.jetty.win32
org.mortbay.servlet
org.mortbay.util
org.mortbay.util.jmx
org.mortbay.xml
org.mortbay.http.handler.jmx
org.mortbay.ftp

Classes:

Main: Main start class. This class is intended to be the main class listed in the MANIFEST.MF of the start.jar archive. It allows an application to be started with the command "java -jar start.jar". The behaviour of Main is controlled by the "org/mortbay/start/start.config" file obtained as a resource or file. This can be overridden with the START system property. The format of each line in this file is: SUBJECT [ [!] CONDITION [AND|OR] ]* where SUBJECT: ends with ".class" is the Main class to run. ends with ".xml" is a configuration file for the command line ends with "/" is a directory from which add ...
Default: The default servlet. This servlet, normally mapped to /, provides the handling for static content, OPTION and TRACE methods for the context. The following initParameters are supported: acceptRanges If true, range requests and responses are supported dirAllowed If true, directory listings are returned if no welcome file is found. Else 403 Forbidden. putAllowed If true, the PUT method is allowed delAllowed If true, the DELETE method is allowed redirectWelcome If true, welcome files are redirected rather than forwarded to. minGzipLength If set to a positive integer, then static content larger than ...
Log: Log formatted and tagged messages. Multiple LogSinks instances can be configured, but by default a System.err sink is created. The Log log format is controlled by the LOG_OPTIONS property supplied to the VM. If LOG_OPTIONS is set, then the default output format is controlled by the option characters in the string: t Timestamp log output T Show the log tag name L Show log label (thread, method and file names). s Show indication of stack depth S Stack trace for each output line (VERY VERBOSE) O Place each log one One line of output If the property LOG_CLASSES is set, it is interpreted as a semi-colon-separated ...
TempByteHolder: Temporary buffer for bytes to be used in situations where bytes need to be buffered but total size of data is not known in advance and may potentially be very large. Provides easy way to access small buffered data as byte[] or String. Enables efficient memory-only handling of small data while automatically switching to temporary file storage when data gets too big to fit in memory buffer. It is highly efficient for both byte-per-byte and block I/O. This class is not a FIFO - you can't mix reading and writing infinitely as all data keep being buffered, not just unread data. Mixing reads and writes ...
Code: Coding Standards support. Support for defensive programming Coding defensively as follows: { ... Code.assertTrue(booleanExpression(),"Assert that expression evaluates true"); ... Code.assertEquals(objectA,objectB,"Assert equality"); Code.assertEquals(1,2,"Assert equality"); ... Code.debug("Debug message"); ... Code.debug("Debug message",exception,object); ... Code.warning("warning message"); ... Code.warning("warning message",exception); ... Code.notImplemented(); Code.fail("fatal error"); ... } The debug output can be controlled with java properties: DEBUG - If set, debug output is enabled DEBUG_PATTERNS ...
Invoker: Dynamic Servlet Invoker. This servlet invokes anonymous servlets that have not been defined in the web.xml or by other means. The first element of the pathInfo of a request passed to the envoker is treated as a servlet name for an existing servlet, or as a class name of a new servlet. This servlet is normally mapped to /servlet/* This servlet support the following initParams: nonContextServlets If false, the invoker can only load servlets from the contexts classloader. This is false by default and setting this to true may have security implications. verbose If true, log dynamic loads * All other ...
Password: Password utility class. This utility class gets a password or pass phrase either by: + Password is set as a system property. + The password is prompted for and read from standard input + A program is run to get the password. Passwords that begin with OBF: are de obfuscated. Passwords can be obfuscated by run org.mortbay.util.Password as a main class. Obfuscated password are required if a system needs to recover the full password (eg. so that it may be passed to another system). They are not secure, but prevent casual observation. Passwords that begin with CRYPT: are oneway encrypted with UnixCrypt. ...
ModelMBeanImpl: Model MBean Implementation. This implementation of the JMX Model MBean API is designed to allow easy creation of Model MBeans. From minimal descriptions of operations and attributes, reflection is used to determine the full signature and ResourceBundles are used to determine other meta data. This class is normally used in one of the following patterns: As a base class for a real MBean that contains the actual attributes and operations of the MBean. Such an Object is only usable in a JMX environment. As a proxy MBean to another non-JMX object. The attributes and operations of the proxied object ...
Page: HTML Page. A HTML Page extends composite with the addition of the HTML Header tags, fields and elements. Furthermore, individual parts of the page may be written or the progressive page be output with flush. Pages contain parameters and named sections. These are used by derived Page classes that implement a Look and Feel. Page users may add to name sections such as "Margin" or "Footer" and set parameters such as "HelpUrl" without knowledge of how the look and feel will arrange these. To assist with standard look and feel creation Page defines a set of standard names for many common parameters and ...
PathMap: URI path map to Object. This mapping implements the path specification recommended in the 2.2 Servlet API. Path specifications can be of the following forms: /foo/bar - an exact path specification. /foo/* - a prefix path specification (must end '/*'). *.ext - a suffix path specification. / - the default path specification. Matching is performed in the following order Exact match. Longest prefix match. Longest suffix match. default. Multiple path specifications can be mapped by providing a list of specifications. The list is separated by the characters specified in the "org.mortbay.http.PathMap.separators" ...
OutputStreamLogSink: A Log sink. This class represents both a concrete or abstract sink of Log data. The default implementation logs to System.err, but other output stream or files may be specified. Currently this Stream only writes in ISO8859_1 encoding. For Other encodings use the less efficient WriterLogSink. If a logFilename is specified, output is sent to that file. If the filename contains "yyyy_mm_dd", the log file date format is used to create the actual filename and the log file is rolled over at local midnight. If append is set, existing logfiles are appended to, otherwise a backup is created with a timestamp. ...
PKCS12Import: This class can be used to import a key/certificate pair from a pkcs12 file into a regular JKS format keystore for use with jetty and other java based SSL applications, etc. usage: java PKCS12Import {pkcs12file} [newjksfile] If you don't supply newjksfile, newstore.jks will be used. This can be an existing JKS keystore. Upon execution, you will be prompted for the password for the pkcs12 keystore as well as the password for the jdk file. After execution you should have a JKS keystore file that contains the private key and certificate that were in the pkcs12 You can generate a pkcs12 file from PEM ...
BindingInterceptor: A BindingInterceptor is responsible for notifying HttpSessionAttributeListeners when Attributes are added to, removed from or replaced in a Session and HttpSessionBindingListeners when attributes are bound into or unbound from a Session. This is an expensive Interceptor to use since it requires that on rebinding an attribute in the Session, the old value is returned in case it is a Listener requiring notification of it's removal.If you are using a distributed store, this requirement will result in a serialisation and network traffic overhead which may not actually be necessary. Unfortunately it ...
TestCase: Test Harness and report. Test Harness for production of standard test reports: Test t1 = new Test("All_Pass"); Test t2 = new Test("All_Fail"); t1.check(true,"Boolean check that passes"); t2.check(false,"Boolean check that fails"); t1.checkEquals("Foo","Foo","Object comparison that passes"); t2.checkEquals("Foo","Bar","Object comparison that fails"); t1.checkEquals(1,1,"Long comparison that passes"); t2.checkEquals(1,2,"Long comparison that fails"); t1.checkEquals(1.1,1.1,"Double comparison that passes"); t2.checkEquals(1.1,2.2,"Double comparison that fails"); t1.checkEquals('a','a',"Char comparison ...
IPAccessHandler: Handler to authenticate access from certain IP-addresses. A server configuration-XML-file can look something like this: <Configure class="org.mortbay.jetty.Server"> ... <Call name="addContext"> ... <Call name="addHandler"> <Arg> <New class="IPAccessHandler"> <Set name="Standard">deny</Set> <Set name="AllowIP">192.168.0.103</Set> <Set name="AllowIP">192.168.0.100</Set> </New> </Arg> </Call> ... This would deny access for everyone except the requests from the IPs 192.168.0.100 and 192.168.0.103.
JDBCUserRealm: HashMapped User Realm with JDBC as data source. JDBCUserRealm extends HashUserRealm and adds a method to fetch user information from database. The authenticate() method checks the inherited HashMap for the user. If the user is not found, it will fetch details from the database and populate the inherited HashMap. It then calls the HashUserRealm authenticate() method to perform the actual authentication. Periodically (controlled by configuration parameter), internal hashes are cleared. Caching can be disabled by setting cache refresh interval to zero. Uses one database connection that is initialized ...
HashUserRealm: HashMapped User Realm. An implementation of UserRealm that stores users and roles in-memory in HashMaps. Typically these maps are populated by calling the load() method or passing a properties resource to the constructor. The format of the properties file is: username: password [,rolename ...] Passwords may be clear text, obfuscated or checksummed. The class com.mortbay.Util.Password should be used to generate obfuscated passwords or password checksums. If DIGEST Authentication is used, the password must be in a recoverable format, either plain text or OBF:. The HashUserRealm also implements SSORealm ...
HttpContext: Context for a collection of HttpHandlers. HTTP Context provides an ordered container for HttpHandlers that share the same path prefix, filebase, resourcebase and/or classpath. A HttpContext is analagous to a ServletContext in the Servlet API, except that it may contain other types of handler other than servlets. A ClassLoader is created for the context and it uses Thread.currentThread().getContextClassLoader(); as it's parent loader. The class loader is initialized during start(), when a derived context calls initClassLoader() or on the first call to loadClass() Note. that order is important when ...
LineInput: Fast LineInput InputStream. This buffered InputStream provides methods for reading lines of bytes. The lines can be converted to String or character arrays either using the default encoding or a user supplied encoding. Buffering and data copying are highly optimized, making this an ideal class for protocols that mix character encoding lines with arbitrary byte data (eg HTTP). The buffer size is also the maximum line length in bytes and/or characters. If the byte length of a line is less than the max, but the character length is greater, than then trailing characters are lost. Line termination is ...
LazyList: Lazy List creation. A List helper class that attempts to avoid unneccessary List creation. If a method needs to create a List to return, but it is expected that this will either be empty or frequently contain a single item, then using LazyList will avoid additional object creations by using Collections.EMPTY_LIST or Collections.singletonList where possible. Usage Object lazylist =null; while(loopCondition) { Object item = getItem(); if (item.isToBeAdded()) lazylist = LazyList.add(lazylist,item); } return LazyList.getList(lazylist); An ArrayList of default size is used as the initial LazyList.
Server: The Jetty HttpServer. This specialization of org.mortbay.http.HttpServer adds knowledge about servlets and their specialized contexts. It also included support for initialization from xml configuration files that follow the XmlConfiguration dtd. HttpContexts created by Server are of the type org.mortbay.jetty.servlet.ServletHttpContext unless otherwise specified. This class also provides a main() method which starts a server for each config file passed on the command line. If the system property JETTY_NO_SHUTDOWN_HOOK is not set to true, then a shutdown hook is thread is registered to stop these ...
Main: Main stop class. This class is intended to be the main class listed in the MANIFEST.MF of the stop.jar archive. It allows an application started with the command "java -jar start.jar" to be stopped. Programs started with start.jar may be stopped with the stop.jar, which connects via a local port to stop the server. The default port can be set with the STOP.PORT system property (a port of < 0 disables the stop mechanism). If the STOP.KEY system property is set, then a random key is generated and written to stdout. This key must be passed to the stop.jar.
ThreadPool: A pool of threads. Avoids the expense of thread creation by pooling threads after their run methods exit for reuse. If the maximum pool size is reached, jobs wait for a free thread. By default there is no maximum pool size. Idle threads timeout and terminate until the minimum number of threads are running. This implementation uses the run(Object) method to place a job on a queue, which is read by the getJob(timeout) method. Derived implementations may specialize getJob(timeout) to obtain jobs from other sources without queing overheads.
HttpOutputStream: HTTP Http OutputStream. Acts as a BufferedOutputStream until setChunking() is called. Once chunking is enabled, the raw stream is chunk encoded as per RFC2616. Implements the following HTTP and Servlet features: Filters for content and transfer encodings. Allows output to be reset if not committed (buffer never flushed). Notification of significant output events for filter triggering, header flushing, etc. This class is not synchronized and should be synchronized explicitly if an instance is used by multiple threads.
AbstractSessionManager: An Abstract implementation of SessionManager. The partial implementation of SessionManager interface provides the majority of the handling required to implement a SessionManager. Concrete implementations of SessionManager based on AbstractSessionManager need only implement the newSession method to return a specialized version of the Session inner class that provides an attribute Map. If the property org.mortbay.jetty.servlet.AbstractSessionManager.23Notifications is set to true, the 2.3 servlet spec notification style will be used.

Home | Contact Us | Privacy Policy | Terms of Service