You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2011/09/13 15:51:09 UTC
[jira] [Created] (AIRAVATA-100) Workflow Execution Context Header
schema
Workflow Execution Context Header schema
----------------------------------------
Key: AIRAVATA-100
URL: https://issues.apache.org/jira/browse/AIRAVATA-100
Project: Airavata
Issue Type: New Feature
Reporter: Suresh Marru
Assignee: Suresh Marru
A generalized workflow context header schema is required to propagate all persistant service end points and execution context from user->workflowengine->gfac->notifications. Referencing the context header in code donation utils area, a generalized version of workflow execution context has to be created.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AIRAVATA-100) Workflow Execution Context Header
schema
Posted by "Suresh Marru (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru resolved AIRAVATA-100.
-----------------------------------
Resolution: Fixed
The workflow execution context is generalized and used in airavata.
> Workflow Execution Context Header schema
> ----------------------------------------
>
> Key: AIRAVATA-100
> URL: https://issues.apache.org/jira/browse/AIRAVATA-100
> Project: Airavata
> Issue Type: New Feature
> Reporter: Suresh Marru
> Assignee: Suresh Marru
> Fix For: 0.3-INCUBATING
>
>
> A generalized workflow context header schema is required to propagate all persistant service end points and execution context from user->workflowengine->gfac->notifications. Referencing the context header in code donation utils area, a generalized version of workflow execution context has to be created.
--
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] [Closed] (AIRAVATA-100) Workflow Execution Context Header
schema
Posted by "Chathura Herath (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chathura Herath closed AIRAVATA-100.
------------------------------------
> Workflow Execution Context Header schema
> ----------------------------------------
>
> Key: AIRAVATA-100
> URL: https://issues.apache.org/jira/browse/AIRAVATA-100
> Project: Airavata
> Issue Type: New Feature
> Reporter: Suresh Marru
> Assignee: Suresh Marru
> Fix For: 0.3-INCUBATING
>
>
> A generalized workflow context header schema is required to propagate all persistant service end points and execution context from user->workflowengine->gfac->notifications. Referencing the context header in code donation utils area, a generalized version of workflow execution context has to be created.
--
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] [Updated] (AIRAVATA-100) Workflow Execution Context Header
schema
Posted by "Suresh Marru (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru updated AIRAVATA-100:
----------------------------------
Fix Version/s: 0.3-INCUBATING
> Workflow Execution Context Header schema
> ----------------------------------------
>
> Key: AIRAVATA-100
> URL: https://issues.apache.org/jira/browse/AIRAVATA-100
> Project: Airavata
> Issue Type: New Feature
> Reporter: Suresh Marru
> Assignee: Suresh Marru
> Fix For: 0.3-INCUBATING
>
>
> A generalized workflow context header schema is required to propagate all persistant service end points and execution context from user->workflowengine->gfac->notifications. Referencing the context header in code donation utils area, a generalized version of workflow execution context has to be created.
--
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