Home >> All >> recoin >> [ system Javadoc ]

•	recoin.system.session.* (6)

• recoin.system: Javadoc index of package recoin.system.


Package Samples:

• recoin.system.session

Classes:

• ComponentOrder: A ComponentOrder is used to to tell a Component what it should do with a RetrievalContainer in terms of the objects it should try to process and their order. Therefore it contains information as to what objects in the container should be processed, whether any results should be stored inside the container, and if these results - together with a corresponding ComponentOrder - should be forwarded to another component inside the ModuleGroup. A ComponentOrder can have another single ComponentOrder as its parent order and any number of them as child order thus creating a tree structure to implement ...
• RepositoryManager: The RepositoryManager is an abstract superclass for all classes implementing an interface to a RECOIN repository. Non abstract subclasses have to implement the methods declared in this class. This ensures the compatibility of different RepositoryManager implementations. Furthermore, any subclasses have to provide an empty constructor method in order to be dynamically loaded via the Reflection-API at runtime. All methods that access and manipulate data in the repository should throw a RepositoryException if there are any errors or inconsistencies between the representation of the object in the repository ...
• RuntimeManager: The RuntimeManager administrates and observes the runtime components of the application. A RuntimeManager executes orders received from an ApplicationManager object. Because the RuntimeManager is a central object that holds references to all runtime components, all exceptions and logging is handled here.
• RetrievalCycle: The RetrievalCycle represents the execution of a client order inside a RetrievalSession. This class passes a RetrievalContainer to the appropriate ModuleGroups in order to be processed. The state of a RetrievalCycle changes during execution.
• ComponentChain: The ComponentChain contains instructions about the the components that should take part in the RetrievalCycle. A ComponentChain basically is a number of ComponentOrder objects that are adressed at Component objects in Modules.
• RetrievalSession: The RetrievalSession represents the context in which a client can execute its requests, i.e. a nuber of tasks that are carried out in a RetrievalCycle. At the end of the cycle the Session reports back the results to the client.
• ApplicationManager: The ApplicationManager represents the main class of the RECOIN framework. It is used to start the RuntimeManager and provides an administrative interface to configure and control the application, i.e. start and stop procedures.
• MySQLRepositoryManager: The MySQLRepositoryManager class is a direct subclass of the abstract RepositoryManager class. It is used to access and manipulate the data in the RECOIN repository which is stored in relational tables in a MySQL database.
• PropertiesReader: The PropertiesReader is responsible for interpreting the global configuration file of the application. The data gathered from the configuration file can then be used to initiate the RECOIN framework.
• SessionQueue: A SessionQueue provides storage for and access to a number of RetrievalSession objects. Essentially, the SessionQueue behaves like a Vector. This class might be extended in future releases.
• Repository: The Repository class encapsulates information about a repository which holds data about all components and interfaces used in RECOIN.
• SessionManager: The SessionManager is used to administrate multiple RetrievalSession objects which are stored in a SessionQueue.
• MySQLRepositoryManagerTest: A TestCase to test the MySQLRepositoryManager class.

Home | Contact Us | Privacy Policy | Terms of Service