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 2010/12/07 08:03:09 UTC
[jira] Created: (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
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.2
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.
[jira] [Commented] (OODT-70) Add ability for sequential and
parallel task specifications for Workflows
Posted by "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=13054468#comment-13054468 ]
Chris A. Mattmann commented on OODT-70:
---------------------------------------
Committed initial patch in r1139325. Tons more progress to make. So far, I've just started to refactor into the WorkflowProcessor architecture. But still need to implement ParallelProcessor, and then tie in the XML policy updates. Thinking of doing a new style XMLRepoManager, for pure WEngineBased policy, and then also upgrading the existing XMLRepositoryManager a bit.
> 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, 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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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.txt
Here's a ton of progress:
* 90% working loading of Wengine-style workflows
- remaining items are loading conditions
* rename Wengine-style workflows as "PackagedWorkflows" b/c they contain the whole package inside a single file
* tons of logging (via System.out) in this patch (will replace with JDK logging)
* tested with the GranuleMaps workflow in wengine branch here: http://svn.apache.org/repos/asf/oodt/branches/wengine-branch/wengine/src/main/resources/policy/workflows/GranuleMaps.xml
Important ideas and items remaining:
* for sub-workflows, can support right now via
- inline BranchEventTask that sends Event to kick off sub-workflow
- dynamic events added to event repo
* for parallel, can support right now with event mapped to single-task workflows
The above two things can be automatically wired into the repo and I will take care of this.
> 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.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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-70:
----------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: OODT-215
> 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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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.062611.patch.txt
- started to port WEngine-style model repository over to trunk/workflow. Just the WEngineModel repo. Don't have some other patches in place, so can't load all the information present in Wengine, but will work to make those official parts of the workflow model.
> 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, 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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-70:
----------------------------------
Fix Version/s: (was: 0.3)
0.4
> 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.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
[jira] [Resolved] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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.062011.patch.txt
OK rev #1. SequentialProcessor and abstract WorkflowProcessor lives! Thanks to [~bfoster] for the inspiration. Comments welcome.
> 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, 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
[jira] [Commented] (OODT-70) Add ability for sequential and
parallel task specifications for Workflows
Posted by "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=13052153#comment-13052153 ]
Chris A. Mattmann commented on OODT-70:
---------------------------------------
Taking a 2 step approach here:
# support a wengine-policy repo manager that just reads wengine-branch style XML files so it's forward compat.
# evolve the XMLRepositoryManager the way I would like to see it support parallel and sequential per my comment above.
> 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
[jira] Updated: (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ 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.
[jira] [Commented] (OODT-70) Add ability for sequential and
parallel task specifications for Workflows
Posted by "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
[jira] Updated: (OODT-70) Add ability for sequential and parallel
task specifications for Workflows
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-70:
----------------------------------
Attachment: workflow.policy.mockup.xml
- see attached mockup. This mockup includes *both* workflow and task information and condition information in the same file. I'd like to split them out into separate files as part of this work since it will ease the adoption of folks who are using the existing workflow system.
> 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.2
>
> 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.