oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OODT-70) Add ability for sequential and parallel task specifications for Workflows
Date Mon, 04 Jul 2011 17:34:22 GMT

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

Chris A. Mattmann updated OODT-70:
----------------------------------

    Attachment: OODT-70.Mattmann.070411.patch.2.txt

- ok this includes fully working conditions loaded up. 

- only thing left to implement are the event mappings and workflow reanlysis. On it.

> 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

        

Mime
View raw message