Group: Apache Taverna Engine

Core APIs and extension points for the T2 reference manager. This includes the SPIs for external references, translators and publishers.

Core workflow object model for Taverna 2 workflows. Depends on the data layer but nothing else, intended as lightweight platform for applications using Taverna APIs as well as the core for the new enactor and model.

Apache Taverna Activity Test Utilities

A Service for executing Taverna workflows

Apache Taverna Platform Report Service

Apache Taverna Credential Manager API

Implementation of the core workflow object model for Taverna workflows including concrete instances of the workflow definition objects and enactment behaviours.

Implementations of certain SPIs to provide a core set of functionality for the reference management framework. This includes ExternalReference implementations to reference data held in local files and URLs along with the appropriate translate / publish logic. Implementations in this package are tied only to the API, although certain metadata files such as hibernate mappings are also included where appropriate (these will be silently ignored if using a backing store that is not hibernate ...

Apache Taverna Platform Capability API

Apache Taverna Database Configuration API

impl of the Observer pattern

Implementations of the core APIs, not including extension point implementations. This package contains implementations of the data access objects, translator infrastructure etc. The extension point implementations that can be considered as core functionality (files, URLs etc) are held in the taverna-reference-types module.

An Execution Service for executing Taverna workflows using a local Taverna Dataflow Engine

Apache Taverna Credential Manager Impl

Implementation of core extension points to the workflow model

A Service for managing runs of Taverna workflows

In order to properly test OSGi-loaded t2ference modules we need a module that is entire external to t2reference and to the test cases. If the test implementations are included in either the api, core implementations or test modules they will be loaded by the root classloader of the test runner - by putting them in an independent artifact we allow them to be loaded through various SPI discovery mechanisms as they would be in a 'real' environment.

Apache Taverna Services API

Apache Taverna Dataflow Activity

Apache Taverna StringConstant Activity