Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Wed, 2 Jan 2013 19:26:13 +0000 (UTC)
From: "Suresh Marru (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12605093.1346085870216.70507.1357154773285@arcas>
In-Reply-To: <JIRA.12605093.1346085870216@arcas>
References: <JIRA.12605093.1346085870216@arcas>
Subject: [jira] [Updated] (AIRAVATA-547) Feature enhancement to distinguish
 output types printed in stdout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AIRAVATA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru updated AIRAVATA-547:
----------------------------------

    Fix Version/s:     (was: 0.6)
                   0.8
    
> Feature enhancement to distinguish output types printed in stdout
> -----------------------------------------------------------------
>
>                 Key: AIRAVATA-547
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-547
>             Project: Airavata
>          Issue Type: Story
>          Components: GFac, XBaya
>    Affects Versions: 0.4-INCUBATING
>            Reporter: Suresh Marru
>             Fix For: 0.8
>
>
> Currently, the values printed to the stdout are picked up as name value pairs irrespective of the output parameter type. Airavata should consider providing a mechanism if the user wishes to distinguish outputs and handle them separately. For instance, if string is specified, then the value is copied as is. If its File, the value is read in as a local file path. If its URL, then the compute host file transfer url is prefixed. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira