Home >> All >> com >> [ lutris Javadoc ]

•	com.lutris.applet.* (1)	•	com.lutris.appserver.* (199)	•	com.lutris.classloader.* (12)
•	com.lutris.dods.* (88)	•	com.lutris.html.* (6)	•	com.lutris.http.* (15)
•	com.lutris.logging.* (6)	•	com.lutris.mime.* (10)	•	com.lutris.multiServer.* (4)
•	com.lutris.testutil.* (2)	•	com.lutris.util.* (40)	•	com.lutris.xml.* (5)

• com.lutris: Javadoc index of package com.lutris.


Package Samples:

• com.lutris.classloader.tests
• com.lutris.classloader
• com.lutris.html
• com.lutris.http
• com.lutris.http.tests
• com.lutris.logging.tests
• com.lutris.logging
• com.lutris.mime.tests
• com.lutris.mime
• com.lutris.testutil
• com.lutris.util.tests
• com.lutris.util
• com.lutris.dods.builder.engine
• com.lutris.dods.builder.generator.base
• com.lutris.dods.builder.generator.bdo
• com.lutris.dods.builder.generator.datainterface
• com.lutris.dods.builder.generator.dataobject
• com.lutris.dods.builder.generator.datastruct
• com.lutris.dods.builder.generator.query
• com.lutris.dods.builder.generator.sql

Classes:

• MultiClassLoader: Summary: A class loader that can load classes from class files and zip files residing in a specified class path. This class loader can also load resources that reside on the class path and return them as is, as input streams, or as byte arrays. Features: Loads classes from class files and zip files. Finds resources and can return them as is, as input streams and as byte arrays. Loads classes and resources using the specified class path. Class path entries can be URLs, directories, zip files or jar files. A secondary classloader can be specified which is used to locate the class if its not found ...
• ClassPathEntry: Summary: A class path entry which is a URL representing either a local or a remote directory or zip file. Manages all the details for zip file support. For example, local zip files (once opened) are kept open for the lifetime of the entry for increased performance. Features: Supports absolute and relative file names Creates URL entry from given String, File, or URL Adds "/" to end of URL for directories if necessary Knows if URL is zip local or remote Knows if URL is a zip file or directory Keeps ZipFile open if the zip file is local Note: "zip files" are files with ".zip" or ".jar" extensions. ...
• StandardSessionManager: This session manager maintains the mapping between session keys and sessions. It generates secure session keys that are safe to use as cookie values in web applications. It also manages the life of a session. If a session is not used (touched) for a preconfigured amount of time, then it is expired and removed from the session manager. The following parameters can be used to configure the session manager. They should be grouped together in a section, normally SessionManager , which is specified to the constructor. SessionLifetimeMax: {int} The maximum number of minutes a session is valid. If this ...
• Application: Interface used to define a Lutris server application. Each application defines a class that implements this interface. The specific application class serves as an entry and control point for the application. This class is responsible for initializing any application specific resources, including instance of standard services that are needed. The class must have a constructor with a configuration file argument. The class is instantiated from a presentation manager and is used to start and stop the application. This structure allows applications to be started on demand by URL reference, as is required ...
• StandardConnectionAllocator: Manages a pool (set) of connections to a database. The pool is named as a logical database. By naming a pool, this allows connection resource control to be on a finer grain that a database and allows for easier migration to multiple databases. One or more pools can map to the same actual database. A connection considered part of the pool, even if its allocated to a thread. These objects are all publicly accessed via the Database Manager, not directly. If an error occurs in a connection, it is dropped from the pool. The process using the connection has already received an error which aborts the ...
• PagedSessionHome: The StandardSessionManager uses PagedSessionHome to manage a collection of sessions that can be paged to disk. PagedSessionHome will page sessions to disk as soon as a pre-configured threshold of sessions has been reached. Only sessions in the 'passive' state will be paged to disk. If all sessions are in the 'active' state and the threshold has been reached, then a request to create a new session will block until one of the 'active' sessions goes into the 'passive' state. At this point the session that just became 'passive' is paged to disk and a new session is created. Sessions are paged to disk ...
• StandardDatabaseManager: The standard database manager implementation. A database manager manages logical databases. It provides a single object from which database connections, object ids (OIDs), transactions and queries can be obtained. The configuration file specifies what logical database to create. The configuration data is specified as follows: DatabaseManager.Databases - A list of logical SQL database names. DatabaseManager.DefaultDatabase - The default logical database used by this application. Optional, if not specified, then the first entry in "DatabaseManager.Databases" is used. DatabaseManager.Debug - Specify ...
• ConfEditor: Methods used by the Enhydra administration application to read and modify application's config files and servlet properties. Multiple servlets may be edited at once, so the servlet id must be passed in to all functions. To use this class, simply call one of the get methods first. The first get will trigger the reading of the config file (if the servlet is an application), and the fetching of the servlet properties from the ServletManager. Then call the get or set methods in any order. All changes made via the set methods are stored in memory in this class. No changes are made to the application ...
• ConfigFile: ConfigFile is used to manipulate Multiserver configuration (.conf) files. Presents all configuration elements in the form of a keyed table. Configuration elements are grouped by string "keys" according to the function they configure. The syntax is described more formally below. stream ::= entry | stream entry entry ::= key "=" value_list | comment | blank value_list ::= value | value_list "," value value ::= fragment | value "+" fragment fragment ::= key | quoted_string quoted_string ::= (C/C++ style quoted string) key ::= (A string matching [A-Za-z_\./][A-Za-z0-9_-\./]*) comment ::= "#" (any text ...
• DiskPagedSessionHome: The StandardSessionManager uses PagedSessionHome to manage a collection of sessions that can be paged to disk. PagedSessionHome will page sessions to disk as soon as a pre-configured threshold of sessions has been reached. Only sessions in the 'passive' state will be paged to disk. If all sessions are in the 'active' state and the threshold has been reached, then a request to create a new session will block until one of the 'active' sessions goes into the 'passive' state. At this point the session that just became 'passive' is paged to disk and a new session is created. Sessions are paged to disk ...
• Logger: A general-purpose logging facility. It is modeled after syslogd . This is a base class from which an actual implementation is derived. It only defines how log message are written by a client. Where the log message is written and the mechanism for controlling logging is left up to the implementation. This class does not define any of these mechanism and their definition is not necessary for understand how to use this class. Each log message is associate with a facility and has a level assigned to it. A facility is a symbolic (String) name that defines a class of log messages. A level is used to ...
• MultiServer: A stand-alone server. It starts and stops services like the ServletContainer. At startup time a configuration file is read, and it describes what services to start. After this config file is read, and the server is set up, no further action is taken by the server. The thread that ran through main() exits. The Services must create threads, and they are responsible for receiving requests from the outside world and processing them. Normally one of the Servlets will be an administration application. This admin app knows about this class, and so it knows how to talk to the current ConnectionMethods ...
• Enhydra: The Enhydra class provides static methods that allow each application to conviently get at their application object. It also provides access This class implements dynamically scoped global variables, accessed via static methods. Which variable is accessed (and thus which Application object is returned) depends on the flow of control of the program before the access (the call stack). Currently a hashtable keyed on the threads themselves is used to store the different Application, in Java 1.2 threads will have a field already available for storing client data. Normal usage of this class is to call ...
• HttpPresentationServlet: Presentation server implemented as a servlet. Translates servlet requests into HttpPresentationManager requests. There is a one to one correspondence between an instance of this servlet and an Enhydra application. An instance of the application is created by the servlet. The servlet requires a single init parameter `configFile', that contains the path to the application's configuration file. This file must define the following fields: server.classPath - The class path for the application, as a comma seperated list. This should not contain the class path for the Java runtime classes or the Lutris ...
• OutputStreamEventQueue: A queue of "events". Each event is a write to the OutputStream. This class implements both the reader and writer half of the queue. Each "event" is returned as an OutputStreamEventQueueEntry object. The "writer" interface is the set of OutputStream calls. This class extends OutputStream, overriding all the OutputStream methods. All data written to this object is stored up as "events" in an internal queue. Each write is a separate event, so sometimes you will get one event with data followed by one with just a newline. You can pass objects of this class to anything that expects and OutputStream. ...
• DBQuery: Utility for querying object from a database. Allocates connections from the database connection pool, ensures the integrity of those connections, and manages result sets after a query is performed. Returns objects representing data in the database. Example - querying a user: import com.lutris.appserver.server.LBS; import com.lutris.appserver.server.sql.*; DBQuery dbQuery = LBS.getDatabaseManager().createQuery(DATABASE_NAME); // NOTE: class CustomerQuery implements Query { ... } CustomerQuery customerQuery = new CustomerQuery(); String [] loginIds = { "customer1", "customer2" }; try { for (int idx=0; ...
• DBRowUpdateException: DBRowUpdateException is thrown when a CoreDO update fails. Two values are used to uniquely identify a row in a table: oId and version. The executeUpdate() method creates an SQL UPDATE command to write the new values in a CoreDO object back to the correct row in the database. The row is identifed by the oId and version values specified in the WHERE-clause of the UPDATE command. So, if no row has the specified oId and version combination, the UPDATE will fail, and report that 0 rows were updated. Note: other database problems (e.g. disk full) can also cause an UPDATE to fail, but these are rare. ...
• PersistentSessionHome: PersistentSessionHome writes all passive sessions to a database. The sessions are written by serializing all the data (excluding the session manager) that is associated with a session. This requires that the session data and user associated with a session are serializable. PersistentSessionHome should be used by applications that want failover support or that want to run in a clustered environment. The session data is written to a table in the database that is defined as (Informix): CREATE TABLE PersistentSession ( sessionKey VARCHAR(64) NOT NULL, isNew CHAR(1) DEFAULT "1" NOT NULL, timeCreated ...
• Resource: A resource that is a file existing on the local machine or a remote machine. The properties of a resource include file name, location, size, and last-modified time. The location of the resource is represented by a ClassPathEntry and is either a directory or a zip file. The file name, described by a String, is relative to the specified location. The resource size is the file size in bytes and the resource time is the last-modified time of the file in milliseconds. This is an abstract class. All subclasses must determine the size and last-modified time for the resource, and must implement the getInputStream ...
• DataObjectException: DataObjectException class, used by Business Objects, catch all the DataObject Exceptions, will be passed to POs and handled there. Need to state the reasons. Usage: import myapp.business.*; try { some access of DOs } catch (SQLException sqlEx) { if (sqlEx.getSQLState().startsWith("02") && (sqlEx.getErrorCode() == 100)) { String msg = "Update or delete DO is out of synch"; throw new DataObjectException(msg, sqlEx); } else if (sqlEx.getSQLState().equals("S1000") && (sqlEx.getErrorCode() == -268)) { String msg = "Integrity constraint violation"; throw new DataObjectException(msg, sqlEx); } else { ...
• ActKeyValidation: This interface is provided so that some sort of key checking or validation on the right-to-run of a servlet is performed. Note that this isn't the most secure implementation of this schema; as the wily hacker who is trying to circumvent checking can just compile up their own version of whatever calls instantiations of this interface and put it before the original one in the classpath. This class can also be used as an initializer for a check or a set of checks that will be called in the performance of an application to see what level of survice the runner of the application has subscribed to. For ...
• StandardLogicalDatabase: Represents a logical database. Each logical database has a connection allocator and a object id allocator. The standard implementation of a local database is used when the database is described as of type Standard in DatabaseManager.DB. dbname .ClassType The configuration data is specified in the section: DatabaseManager.DB. dbName The following is a description of the sub fields: JdbcDriver - The JDBC driver to use to access that database. Manditory. E.g. "intersolv.jdbc.sequelink.SequeLinkDriver" Connection - This section is passed onto the connection allocator. See for details on connection ...
• BasicAuth: Methods to be used to implement the HTTP Basic Auth authorization method. This is the standard username/password mechanism in use all over the web. Note: the username and password are sent over the net base64 encoded, which is practically clear text. So this method is no more secure than the communication channel being used. Usage: When a request comes in, before responding to it, call getAuthentication() . It will return the username and password that was sent along with the request. If no authorization was sent, null is returned. The caller is then responsible for deciding if the username and ...
• StandardSessionHome: StandardSessionManager uses StandardSessionHome to manage a collection of sessions. StandardSessionHome acts both as a session factory and as a session repository. The session manager gains access to instances of sessions via the home (StandardSessionHome) interface. The session manager dynamically loads the home interface. The implementation of the home interface that is loaded is specified in the applications configuration file: SessionHome.Class: {class name} StandardSessionHome manages the state of a session. A session exists in either of two states: 'active' or 'passive'. An 'active' session ...
• DBTransaction: Used to perform database transactions. Example - adding a new user: import com.lutris.appserver.server.LBS; import com.lutris.appserver.server.sql.*; DBTransaction transaction = LBS.getDatabaseManager().createTransaction(DATABASE_NAME); // NOTE: class CustomerDO implements Transaction { ... } // NOTE: An Object ID is automatically calculated by the constructor. CustomerDO customer = new CustomerDO(); customer.setFirstName("Santa"); customer.setLastName("Claus"); // ... set all other CustomerFields ... // // Now add the new object to the database. // try { transaction.insert(customer); transaction.commit(); ...

Home | Contact Us | Privacy Policy | Terms of Service