You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2016/05/31 00:11:12 UTC

[jira] [Commented] (TAVERNA-254) provenance depends on xml serialization

    [ https://issues.apache.org/jira/browse/TAVERNA-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307026#comment-15307026 ] 

Stian Soiland-Reyes commented on TAVERNA-254:
---------------------------------------------

The workaround is that the classic provenance layer is not active in Taverna 3.

> provenance depends on xml serialization
> ---------------------------------------
>
>                 Key: TAVERNA-254
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-254
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Engine
>            Reporter: Stian Soiland-Reyes
>            Priority: Blocker
>             Fix For: engine 3.1.0
>
>
> The current provenance engine depends on the guts of how T2flow is serialized to XML (for storage in the DB). _This is Wrong._ We should not be saving that sort of thing out. Instead, the provenance code should be making use of the workflow bundle package.
> The code is also not OSGIfied (with singleton dependencies) but that's less critical given that what it's doing is entirely wrong anyway.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)