You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Marlon Pierce (Created) (JIRA)" <ji...@apache.org> on 2012/03/28 14:12:28 UTC

[jira] [Created] (AIRAVATA-353) WorkflowExecution interface only accesses outputs, not inputs

WorkflowExecution interface only accesses outputs, not inputs
-------------------------------------------------------------

                 Key: AIRAVATA-353
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-353
             Project: Airavata
          Issue Type: Improvement
            Reporter: Marlon Pierce


The WorkflowExecution interface (in org.apache.airavata.registry.api) only supports getOutput() operations.  Is there a design reason why it doesn't support getInput() operations?  I'd like to use this object to query the registry for both input and output associated with a workflow run.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (AIRAVATA-353) WorkflowExecution interface only accesses outputs, not inputs

Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake resolved AIRAVATA-353.
-----------------------------------------

    Resolution: Invalid

This issue is obsolete !

Lahiru
                
> WorkflowExecution interface only accesses outputs, not inputs
> -------------------------------------------------------------
>
>                 Key: AIRAVATA-353
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-353
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Marlon Pierce
>
> The WorkflowExecution interface (in org.apache.airavata.registry.api) only supports getOutput() operations.  Is there a design reason why it doesn't support getInput() operations?  I'd like to use this object to query the registry for both input and output associated with a workflow run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira