Indexed Artifacts (13.9M)

Popular Categories

Group: SF Taverna T2 Core

Sort: popular | newest

1. Workflow Model API72 usages

net.sf.taverna.t2.core » workflowmodel-apiLGPL

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.
Last Release on Sep 5, 2012
Implementation of the core workflow object model for Taverna 2 workflows including concrete instances of the workflow definition objects and enactment behaviours.
Last Release on Sep 5, 2012
Core APIs and extension points for the T2 reference manager. This includes the SPIs for external references, translators and publishers.
Last Release on Sep 5, 2012
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 ...
Last Release on Sep 5, 2012
Implementations of the core APIs, not including extension point implementations. The extension point implementations that can be considered as core functionality (files, URLs etc) are held in the t2reference-core-extensions package. This package contains implementations of the data access objects, translator infrastructure etc.
Last Release on Sep 5, 2012
Database Storage and Analysis of Provenance Info
Last Release on Sep 5, 2012

7. Derby Provenance5 usages

net.sf.taverna.t2.core » provenance-derbyLGPL

Derby Provenance
Last Release on Sep 5, 2012

8. MySQL Provenance3 usages

net.sf.taverna.t2.core » provenance-mysqlLGPL

MySQL Provenance
Last Release on Sep 5, 2012
Implementation of Core Extension Points to The Workflow Model
Last Release on Sep 5, 2012


In order to properly test the raven-aware functionality within the t2reference 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 implementation 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 raven's various SPI discovery mechanisms as they would be in a 'real' environment.
Last Release on Sep 5, 2012