*

Overview

This package contains a number of useful classes for working with the Managed Object Framework. A brief description of the classes follows. Most of the classes listed below have more detailed documentation in Javadoc form, this write up is just intended to provide an overview of what is available.

Related Documents

  • Encoded Data Overview
  • URLs and Object Names
  • Base Object Overview
  • Contents

  • ObjectResolver
  • Base Classes
  • Key Processing
  • MOFW Collections
  • Iterators
  • Encoded Stream Support
  • Memory Based Streams
  • ObjectResolver

    The ObjectResolver interface provides a very neutral interface for mapping objects to and from string names to support such facilities as remote-method-call. It has just two methods, findObject, and getKeyPath. findObject takes an object string name (called a keyPath), and an optional class/interface name. It is supposed to return the object that has that name. The optional class/interface name may be used to verify that the object supports a particular interface. getKeyPath takes an object and returns the keyPath that can later be used to look up the object with findObject.

    ObjectResolverKC is an implementation of the ObjectResolver interface that uses a collections from the MOFW to support the mapping process.

  • ObjectResolver - Interface
  • ObjectResolverKC - Class
  • Base Classes

    The base classes provide partial implementations of important parts of the MOFW. These are described in detail in Overview of the Base Classes,

  • BaseAO - Abstract Class
  • BaseMO - Abstract Class
  • BaseQC - Abstract Class
  • BaseKC - Abstract Class
  • BaseBC - Abstract Class
  • BaseNC - Abstract Class
  • BaseRC - Abstract Class
  • BaseIterator - Abstract Class
  • BaseCommandOn - Abstract Class
  • Key Processing

    The key processing classes support working with various string forms of object identifiers. Currenty the only form supported is the MOFW key path string which is a slash separated sequence of keys. Soon we will add support for URL-base object identifiers.

  • KeyPath - Class
    Provides a set of methods for parsing and constructing key path strings. The methods are designed to make it easy to process a key path sequentially and to get the details of leading slashes and such right.
  • MOFW Collections

    The MOFW collections provide complete implementations of some of the collection types used in the MOFW. Each of these not only supports there required interfaces, but they also support all the interfaces for application objects (Lifecycle, Identifiable, Manageable, IdentityDelegator, Dependent).
  • HashtableNC - Class
    A NamedContext that uses a java.util.Hashtable for its internal data structure.
  • VectorRC - Class
    A ReferenceCollection that uses a java.util.Vector for its internal data structure.
  • Iterators

    MOFW defines Iterators to return results from such MOFW methods as QueryableCollection.evaluate. These classes provide complete implementations of Iterators that can be used in implementing methods that must return Iterators.
  • EnumerationIterator - Class
    An Iterator that uses a java.util.Enumeration as its constructor argument. This iterator does not support random access or backward access.
  • VectorIterator - Class
    An Iterator that uses a java.util.Vector as its constructor argument. This Iterator fully supports full random and bi-directional access.
  • Encoded Stream Support

    This collection of classes provides a very flexible framework for supporting MOFW EDStreams that need to consume or produce data encoded in character sequences. In addition to the framework there are complete implementations of some encodings (Currently on 7-bit ASCII encodings are supported, but URL encodings will be added soon). Users of the encoding implementation do not need to understand or work with the framework. These classes and the encoding schemes are described in detail in
    Overview of Encoded Streams.

    Memory Based Stream

    There are two memory based streams, one based on an array and the other based on a Vector. Each of these implement the full EDStream interface for both input and output. The do not actually read or write data to external storage, but just to an internal memory buffer. These are quite efficient for usage in transfering essential state from one object to another object, such as in a copy operation.

  • ObjectEDStream - Abstract Class
  • VectorEDStream - Class
  • EnumInputEDStream - Class