You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/19 05:28:47 UTC

[jira] [Updated] (OODT-210) Support graph-based workflows using nextTask tags

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

Chris A. Mattmann updated OODT-210:
-----------------------------------

    Issue Type: Sub-task  (was: Improvement)
        Parent: OODT-215

> Support graph-based workflows using nextTask tags
> -------------------------------------------------
>
>                 Key: OODT-210
>                 URL: https://issues.apache.org/jira/browse/OODT-210
>             Project: OODT
>          Issue Type: Sub-task
>          Components: workflow manager
>         Environment: from JPL's internal JIRA, pre-Apache
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> One way to support graph based workflows in the WM (which currently only supports pipeline workflows natively) would be to add a nextTask (or branch) tag that can accept multiple values to the workflow model. In essence this allows a graph to be specified that will allow parallel branches/etc. and a more graph based workflow model.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira