[
https://issues.apache.org/jira/browse/OODT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-70.
-----------------------------------
Resolution: Fixed
- resolved the last part of this patch in r1142815.
I took care of the last action items, including:
- parallel workflows end up being attached to the same event as the original
workflow (so they execute in parallel because events can map to multiple
workflows). The original workflow (a meta-workflow if you will) is removed from
the event map and from the workflow list at that point.
- sub-workflows are taken care of through a virtual redirector task. This is
the start of the work for OODT-211, but not all of it.
I added a unit test for regression with some basic checks against the more
complicated parts of the structure parsing.
Phew. This was a PAIN :-) I found a lot of stuff though that I like that
[~bfoster] did. Really awesome stuff. In this order:
* workflows can have conditions -- love this.
* workflow task configurations (and workflow configurations) are just metadata.
No need for special objects.
* the graph structure truly is the way to go (and I wired it into the innards
of the PackagedWorkflowRepository so we should pull it out later).
> Add ability for sequential and parallel task specifications for Workflows
> -------------------------------------------------------------------------
>
> Key: OODT-70
> URL: https://issues.apache.org/jira/browse/OODT-70
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Environment: indep. of env.
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.4
>
> Attachments: OODT-70.Mattmann.062011.patch.txt,
> OODT-70.Mattmann.062611.patch.txt, OODT-70.Mattmann.070411.patch.2.txt,
> OODT-70.Mattmann.070411.patch.txt, workflow.policy.mockup.xml
>
>
> There has been a lot of internal JPL work on flushing out new ideas with the
> workflow manager. One of those new ideas is to explicitly support
> differentiating between different types of
> {code}org.apache.oodt.cas.workflow.WorkflowTask{code} entities, classifying
> them as *sequential* (their current form) versus *parallel* (those that deal
> explcitly with branch and bound). Even though the current workflow system can
> support these activities, they are largely code-based and require
> modification and intrinsic knowledge of the Workflow event system.
> It would be nice to simplify this for the users and allow task.xml,
> conditions.xml and *.workflow.xml files (or explicit WorkflowRepos) to
> support this nomenclature.
> I'll attach a proposed spec of what the updated XML files would look like
> using this paradigm. Then my goal is to take the existing workflow system and
> augment it with this functionality.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
