[
https://issues.apache.org/jira/browse/AIRAVATA-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Gunathilake resolved AIRAVATA-403.
-----------------------------------------
Resolution: Fixed
Done !
Lahiru
> Workflow Execution Context should be used for all workflow executions
> ---------------------------------------------------------------------
>
> Key: AIRAVATA-403
> URL: https://issues.apache.org/jira/browse/AIRAVATA-403
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata Client, GFac, Workflow Interpreter, XBaya
> Affects Versions: 0.3-INCUBATING
> Reporter: Suresh Marru
> Fix For: 0.4-INCUBATING
>
>
> Workflow execution context allows to specify all meta information related to
> workflow executions, like scheduling, user, output data, security context and
> so on. There is a well defined schema defined for WEC -
> https://svn.apache.org/repos/asf/incubator/airavata/trunk/modules/commons/workflow-execution-context/.
> The client API should be able to set the required values and workflow engine
> passes this in the soap header when making a web service invocation, or
> should set it as a context object and send it for gfac embeded mode executions
--
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
