Package edu.iu.iv.core.persistence

The persistence layer serves to fulfill all the persistence needs of the system.

See:
Description

Interface Summary

DatabaseResourceDescriptor	A descriptor that holds all data necessary for persisteing to and restoring from a database.
FileResourceDescriptor	A descriptor for a data resource represented as a file on disk.
PersistenceRegistry	Holds all the available registered Persisters in the IVC.
Persister	A Persister is responsible for saving and restoring models to and from a resource.
ResourceDescriptor	The ResourceDescriptor is the top level interfaces from which all other ResourceDescriptors are derived, such as FileResourceDescriptor.

Class Summary

PersisterProperty

This class defines properties that each persister can choose to provide.

Exception Summary

IncorrectFormatException	An IncorrectFormatException is thrown by a persister whenever the data that it expects is different from what it actually finds in the resource descriptor.
PersistenceException	All exceptions that are not java Exceptions must be PersistenceException.
PersisterNotFoundException	Signifies the exception that a Persister was not found.

Package edu.iu.iv.core.persistence Description

The persistence layer serves to fulfill all the persistence needs of the system. This layer allows the details of storing data to file and restoring them to objects to be hidden, allowing users to concentrate on the design, implementation and optimization of algorithms.

There are two main interfaces for the sake of practical usage: the PersistanceFacade and the PersistenceRegistry. The facade is intended to make life easier for those who do not want to be concerned about the specifics of the persisters. The registry is intended to provide more lower level access to each of the persisters available in the system. Normally, the facade would be used by the normal users while coding up algorithms, while the registry would be used by user-interface based systems which allow the user to choose between several choices. For details, see the documentation of the individual classes and interfaces.