You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Paul Ramirez (JIRA)" <ji...@apache.org> on 2011/01/18 02:21:58 UTC

[jira] Updated: (OODT-70) Add ability for sequential and parallel task specifications for Workflows

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

Paul Ramirez updated OODT-70:
-----------------------------

    Fix Version/s:     (was: 0.2)
                   0.3

Pushing off to 0.3 release.

> 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: Improvement
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.3
>
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.