ADK CVS

Package tryllian.are.persistence.spi

This package contains the Service Provider Interface, which defines how a new persistence plugin can be written.

See:
          Description

Interface Summary
AgentBuilder The AgentBuilder is an interface by which plugins can reconstruct agents without having to know about the internal structure of agents.
AgentPersistencePlugin Objects that implement the AgentPersistencePlugin are created by the PersistencePlugin and manage the persisting of the agent data.
AgentSerializer The AgentSerializer is an interface by which persistence plugins can obtain data about an agent.
ARLBuilder The ARLBuilder is the counterpart of the ARLSerializer.
ARLPersistencePlugin Objects that implement the ARLPersistencePlugin are created by the PersistencePlugin and manage the persisting of the AgentResourceLocator data (proxied by the ARLSerializer).
ARLSerializer The ARLSerializer is a proxy for an AgentResourceLocator.
JNDIPersistencePlugin The JNDIPersistencePlugin handles the persistent storage needs of the JNDI component of the ARE.
PersistencePlugin The PersistencePlugin defines the general contract for external persistence plugins.
Transaction The Transaction models a transaction over multiple methods in the PersistencePlugin.
 

Class Summary
PersistencePermission The PersistencyPermission gives code access to the persistence backend.
 

Exception Summary
PersistenceException The PersistenceException is used to signal persistence exceptions.
 

Package tryllian.are.persistence.spi Description

This package contains the Service Provider Interface, which defines how a new persistence plugin can be written.

The package contains two kinds of interfaces: interfaces that have to be implemented by the plugin writer and interfaces whose implementation will be provided by the ARE to the plugin. The latter interfaces are used to hide the internals of agent building from the plugin writer.

The interfaces that need not be implemented by the Service Provider are

Objects implementing these interfaces will be provided to the plugin when required.

Note that persistency is transaction based. The general procedure followed by the ARE is as follows:

  1. Obtain a Transaction object from the plugin
  2. Operate on the Transaction object by calling methods from the plugin
  3. Use the Transaction to commit or rollback all changes.


Copyright 2005, Tryllian Solutions B.V.