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 02:02:47 UTC
[jira] [Created] (OODT-205) WorkflowInstances should have
pre-conditions as well
WorkflowInstances should have pre-conditions as well
----------------------------------------------------
Key: OODT-205
URL: https://issues.apache.org/jira/browse/OODT-205
Project: OODT
Issue Type: Improvement
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
[jira] [Commented] (OODT-205) WorkflowInstances should have
pre-conditions as well
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084790#comment-13084790 ]
Chris A. Mattmann commented on OODT-205:
----------------------------------------
- made a ton of progress towards this in r1157470. In fact, I've done everything but implement the engine part of it. To implement this in the current workflow engine, I'm tempted to "fake it" by firing off the workflow instance, but immediately putting it into paused state by adding a "virtual first task" with the workflow's conditions attached to it. The task would be a No-Op, so as soon as the conditions are true, the workflow would enter its "real" first task, and then be on with it.
> 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
[jira] [Updated] (OODT-205) WorkflowInstances should have
pre-conditions as well
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-205:
-----------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: OODT-215
> 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
[jira] [Resolved] (OODT-205) WorkflowInstances should have
pre-conditions as well
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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