[
https://issues.apache.org/jira/browse/OODT-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432844#comment-13432844
]
Sheryl John commented on OODT-484:
----------------------------------
So these lifecycle XML files would have default States and Stages for a
workflow that a user can reuse for every workflow, right? A user would need to
only edit these files if he/she wants to add or delete states/stages or to
change priorities and mappings.
Would there be a lifecycle at workflow Id level? If yes, then I'll have to edit
all lifecycle files instead of one for every workflow defined. Did I understand
this right?
> Enhance Workflow Lifecycle to include state change logic
> --------------------------------------------------------
>
> Key: OODT-484
> URL: https://issues.apache.org/jira/browse/OODT-484
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Affects Versions: 0.4
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
