airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-547) Feature enhancement to distinguish output types printed in stdout
Date Sun, 30 Mar 2014 04:27:15 GMT

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

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

    Affects Version/s:     (was: 0.13)
                       WISHLIST
             Assignee:     (was: Suresh Marru)
               Labels: contributors  (was: )

Until the java swing xbaya is used, we can keep this in wishlist. If we fully move to web
based monitoring tools, we can mark this won't fix. 

> 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: WISHLIST
>            Reporter: Suresh Marru
>              Labels: contributors
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message