Package org.biomoby.client

The components used for developing Moby clients.

See:
Description

Interface Summary

MobyRequestEventHandler	This interface is used for callbacks when MobyRequest is acting as a server or client.
SimpleCache	An interface defining basic operation for caching data.
SimpleFileCache	An interface extending basic operations for caching data by pointing users directly to files with cached objects or for cached objects.

Class Summary

AsyncClient	Implements the client side of the asynchonous SOAP-based MOBY service invocation specification.
BaseClient	This is a base class for Biomoby clients.
BaseCmdLineClient	This is a base class for the command-line driven clients.
CentralCachedCallsImpl	Implements the functionality of caching by reusing identical calls to MOBY central (e.g. asking multiple times what services take a DNA sequence in the gi namespace).
CentralDigestCachedImpl	An implementation of CentralAll, allowing to cache locally results of the cumulative methods so it does not need to access Moby registry all the time.
CentralDigestCachedSimpleImpl	An implementation of CentralAll, allowing to cache locally results of the cumulative methods so it does not need to access Moby registry all the time.
CentralDigestImpl	A default implementation of CentralDigest to get (also) cumulated data from a Moby registry.
CentralImpl	A default implementation of the interface Central allowing access to a Moby registry.
CmdLineHelper	An abstract parent of various command-line tools.
DataServiceEdge	An instance of this class is a container for a pair of a data type and a Moby service definitions, and for an information how they can be connected.
DataTypeConnector	A simple container for a connection between two data types.
ExtendedProtocolClient	A client that can (additionally to the normal features) communicate with an implementation of a Biomoby service using a non-biomoby protocol.
ExtendedServiceLocator	An extended container allowing to store information how to call a biomoby service using non-biomoby protocols.
FileCache	A simple cache implementation to save and later return (any) data, or to find that the given data are not available in the cache.
FilterDataTypes	Utilities for dealing with a set of MobyDataTypes.
FilterServices	This class allows to filter a set of services using some criteria.
GraphsServlet	A servlet making graphs of Moby service instances, Moby data types, and Moby service types.
Graphviz	A utility class that understands how to create graphviz graphs from a set of ServiceEdges, or from other data structures.
MobyRequest	This class handles the WSDL transaction to request a response from a remote SOAP Web service that handles the MOBY format.
MobyRequestEvent	This is the event passed to a MobyRequestEventHandler, representing either data for a request for service, or the data from a service response depending on whether the listener registered itself in a client or server.
MobyServiceLocator	A container for information how to reach a Biomoby service.
RDF	A utility class that understands how to create graphviz graphs from a set of ServiceEdges, or from other data structures.
ServiceConnections	This class contains knowledge (an algorithm) how individual Moby services could be connected together based on their input and output data types.
ServicesEdge	An instance of this class is a container for a pair of Moby service definitions, and for an information how they can be connected.
ServletFileCache	A simple cache implementation meant to be used in a servlet environment in order to save and later return (any) data, or to find that the given data are not available in the cache.
Taverna	A utility class that understands how to create workflow definitions for Taverna.

Package org.biomoby.client Description

The components used for developing Moby clients. The Moby clients can be both clients of the Moby registry and clients of the Moby services.

The most important class is CentralImpl implementing interface Central and by doing so hiding all Moby complexity (and changes) under the hood.