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

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051990#comment-13051990 ] 

Chris A. Mattmann commented on OODT-70:
---------------------------------------

Thinking about this more, I'm not a fan of having execution="sequential" or execution="parallel" versus <parallel> and <sequential> as tags. It would be nice to stick to one or the other.

> 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: 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