Mailing-List: contact dev-help@taverna.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@taverna.incubator.apache.org
MIME-Version: 1.0
References: <CAMBJEmV1jkeZTf-Qr6SsKxcGOL5uULx=E+-EL67xbZ0cswrFgg@mail.gmail.com>
In-Reply-To: <CAMBJEmV1jkeZTf-Qr6SsKxcGOL5uULx=E+-EL67xbZ0cswrFgg@mail.gmail.com>
From: Gale Naylor <GaleN@noventussolutions.com>
Date: Wed, 04 May 2016 17:24:26 +0000
Message-ID: <CAOMUzGcSKNSUnGvjN+j4VgytRYUjBhw22utWbc0zxJuww1w36Q@mail.gmail.com>
Subject: Re: How does the Taverna Engine run a workflow?
To: dev@taverna.incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b33cabcee8ae10532077f7c
archived-at: Wed, 04 May 2016 17:24:42 -0000

--047d7b33cabcee8ae10532077f7c
Content-Type: text/plain; charset=UTF-8

Thanks for the doc update, Stian!

On Wed, May 4, 2016 at 10:21 AM Stian Soiland-Reyes <stain@apache.org>
wrote:

> I tried to document the modules of Taverna Engine
>
> https://github.com/apache/incubator-taverna-engine/#modules
>
> and added a walk-thru of how these modules interact when running a
> workflow through the Taverna Platform API:
>
> https://github.com/apache/incubator-taverna-engine/#which-module-does-what
>
>
>
> I must admit it seems a bit excessive - e.g. the role of T2Reference
> has now diminished with the Platform's use of the Bundle and that we
> removed the (inefficient and license-incompatible) Hibernate storage.
>
> This is partially caused by previously keeping Taverna Platform as a
> separate overlay of the Taverna Engine which remained mainly Taverna 2
> compatible for the Activity implementations.
>
>
> Now we maintain them together under taverna-engine we can be a bit
> more brave. After this release we can consider how we can
> de-complicate some of this :)
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>

--047d7b33cabcee8ae10532077f7c--