[jira] [Commented] (TAVERNA-939) Use taverna-baclava-language parser to vaildate workflow

["Alan R Williams (JIRA)" <ji...@apache.org>]

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

Alan R Williams commented on TAVERNA-939:
-----------------------------------------

I do not think it is an issue with validation of the *workflow*. The workflow and the baclava may both be valid. The issue is that there is insufficient information to start the workflow run (missing input values), but the command line tool starts the workflow running with whatever input port value settings it finds (if any). Because there are some missing values, the workflow run hangs waiting for the values to pass into activities.

There is an edge case where this would not matter i.e. where the value-less input was not attached to any activity. This may be worth checking to ensure my theory is correct

> Use taverna-baclava-language parser to vaildate workflow
> --------------------------------------------------------
>
>                 Key: TAVERNA-939
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-939
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Commandline, Taverna Server
>    Affects Versions: commandline 3.1.0, server 3.1.0
>            Reporter: Ian Dunlop
>            Priority: Minor
>
> An issue was reported (see http://markmail.org/message/3souha26uva4vi7z) where you could upload a workflow to Taverna server which had different input ports to the ones you specified and it would still run but never finish. This suggests that the workflow is not validated by the server. Since the server wraps the command line it would seem that the commandline module should be improved to use taverna-baclava-language to validate the workflow.



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