[
https://issues.apache.org/jira/browse/AIRAVATA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Marru closed AIRAVATA-500.
---------------------------------
Resolution: Later
My personal opinion is this is a corner case. But if this is asked for again,
one way to do is to construct as hierarchal workflows. The master workflow
invokes the child workflow using Airavata API which should facilitate
specifying paramaters like executable paths.
I am marking the resolution as 'Later' and closing it, so we can find all
issues marked 'later' for future consideration.
> Set the executable path dynamically from Workflow context
> ---------------------------------------------------------
>
> Key: AIRAVATA-500
> URL: https://issues.apache.org/jira/browse/AIRAVATA-500
> Project: Airavata
> Issue Type: New Feature
> Components: GFac, Workflow Interpreter, XBaya
> Affects Versions: 0.4-INCUBATING
> Reporter: Raminderjeet Singh
>
> DES project initial scripts selects which executables to run based on
> simulation size. Executable paths are returned to workflow as service outputs
> and need to be set into workflow context and GFAC provider need to read
> context header to set executable path.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
