Stian Soiland-Reyes commented on TAVERNA-1013:

I wonder if the problem can be because you have Activity Output Ports called 
"aresponseBody" and "astatus" - but the REST activity will deliver "status" and 

Hence no output will be delivered from the processor binding and the processor; 
and no output is delivered at the output port.

However this is no excuse for why the executeworkflow "runs forever" (it is 
waiting for an output that never comes) so this remains a bug; I would have 
thought that the AbstractActivity would insert errors for any missing outputs, 
as it does at say a Beanshell script with wrong output ports specified.

> The workflow created by Taverna 3 not run
> -----------------------------------------
>                 Key: TAVERNA-1013
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-1013
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Command-line Tool
>    Affects Versions: command-line 3.1.0
>         Environment: windows 
>            Reporter: Mashael
>             Fix For: command-line 3.2.0
>         Attachments: rest1.t2flow, rest1.wfbundle.zip, source_code.txt, 
> test87.wfbundle.zip
> I have created the same workflow in Taverna 2 which use REST, and can be run, 
> and I was trying to make the same workflow in Taverna 3 but could not be run.

This message was sent by Atlassian JIRA

Reply via email to