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/08/14 09:08:27 UTC

[jira] [Resolved] (OODT-205) WorkflowInstances should have pre-conditions as well

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

Chris A. Mattmann resolved OODT-205.
------------------------------------

    Resolution: Fixed

- I implemented my suggestion in r1157478, and simply add a virtual task to the head of the workflow called "global-conditions-workflow name" and seed it with the workflow global conditions. Works perfectly. Unit tests updated to check for this in all 3 repos too for coverage. 

> WorkflowInstances should have pre-conditions as well
> ----------------------------------------------------
>
>                 Key: OODT-205
>                 URL: https://issues.apache.org/jira/browse/OODT-205
>             Project: OODT
>          Issue Type: Sub-task
>          Components: workflow manager
>         Environment: From JPL's old internal JIRA, before apache move
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> WorkflowInstances, like WorkflowTasks, are just a specialized data-flow execution sequence. In many cases, you want a set of global (pre-)conditions to all be true in order to execute an entire sequence of WorkflowTasks. In this case, it would make a lot of sense to have WorkflowInstance-level conditions.

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