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-484) Enhance Workflow Lifecycle to include state change logic
Date Fri, 14 Dec 2012 00:34:32 GMT

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

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

    Fix Version/s:     (was: 0.5)
                   0.6

- push out to 0.6
                
> Enhance Workflow Lifecycle to include state change logic
> --------------------------------------------------------
>
>                 Key: OODT-484
>                 URL: https://issues.apache.org/jira/browse/OODT-484
>             Project: OODT
>          Issue Type: Improvement
>          Components: workflow manager
>    Affects Versions: 0.4
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Brian Foster
>            Priority: Minor
>             Fix For: 0.6
>
>
> Let's split up the lifecycle XML file into several files (kind have it look like filemgr
element and product-type XML files):
>   1) Define States XML file
>   2) Define Stages XML file
>   3) Mapping of States to Stages XML file
>   4) Mapping of States to next valid States
> I then propose we add a Priority to each Stage (its purpose will become apparent)...
Then we create a new Interface: StatePreCondition... These preconditions would then be attached
to a State... Then when the Workflow Processor detects a sub-processor State change it would
poll each next valid State (determined by mapping in purposed XML file #4) for their PreConditions
and if any of the State's PreConditions pass then that State would become the next State of
that Workflow Processor (if multiple States pass as next State, then the priority attached
to the Stage each State belongs to is used to determine which State becomes next State)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message