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:16:47 UTC
[jira] [Created] (OODT-209) Workflow Manager Dynamic Workflows
Workflow Manager Dynamic Workflows
----------------------------------
Key: OODT-209
URL: https://issues.apache.org/jira/browse/OODT-209
Project: OODT
Issue Type: Improvement
Components: workflow manager
Environment: From JPL's internal JIRA pre-ASF
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Fix For: 0.4
Right now, WorkflowInstances, sequences of WorkflowTasks, turned into an executable unit, are triggered by an event name, mapped to a particular Workflow model, which gets turned into a WorkflowInstance. In reality, it makes a lot of sense to have the ability to simply dynamically execute sequences of WorkflowTasks, without any event name indirection, or Workflow model indirection, a sort of "dynamic" Workflow capability. This would add the ability for the Workflow Manager to execute a sequence of WorkflowTasks (identified by their taskIds, which must exist in the WorkflowRepository), that are subsequently turned dynamically into a Workflow model, and then into a WorkflowInstance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OODT-209) Workflow Manager Dynamic Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-209.
------------------------------------
Resolution: Fixed
- addressed in r1156658.
> Workflow Manager Dynamic Workflows
> ----------------------------------
>
> Key: OODT-209
> URL: https://issues.apache.org/jira/browse/OODT-209
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Environment: From JPL's internal JIRA pre-ASF
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
>
> Right now, WorkflowInstances, sequences of WorkflowTasks, turned into an executable unit, are triggered by an event name, mapped to a particular Workflow model, which gets turned into a WorkflowInstance. In reality, it makes a lot of sense to have the ability to simply dynamically execute sequences of WorkflowTasks, without any event name indirection, or Workflow model indirection, a sort of "dynamic" Workflow capability. This would add the ability for the Workflow Manager to execute a sequence of WorkflowTasks (identified by their taskIds, which must exist in the WorkflowRepository), that are subsequently turned dynamically into a Workflow model, and then into a WorkflowInstance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-209) Workflow Manager Dynamic Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-209:
-----------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: OODT-215
> Workflow Manager Dynamic Workflows
> ----------------------------------
>
> Key: OODT-209
> URL: https://issues.apache.org/jira/browse/OODT-209
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Environment: From JPL's internal JIRA pre-ASF
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
>
> Right now, WorkflowInstances, sequences of WorkflowTasks, turned into an executable unit, are triggered by an event name, mapped to a particular Workflow model, which gets turned into a WorkflowInstance. In reality, it makes a lot of sense to have the ability to simply dynamically execute sequences of WorkflowTasks, without any event name indirection, or Workflow model indirection, a sort of "dynamic" Workflow capability. This would add the ability for the Workflow Manager to execute a sequence of WorkflowTasks (identified by their taskIds, which must exist in the WorkflowRepository), that are subsequently turned dynamically into a Workflow model, and then into a WorkflowInstance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira