[
https://issues.apache.org/jira/browse/OODT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455311#comment-13455311
]
Chris A. Mattmann commented on OODT-495:
----------------------------------------
Lots of progress in r1384539:
- OODT-495: WIP
- start to flesh out WorkflowProcesor nextState function (1/4 implemented;
need pre/post cond status eval; move status checkoff to EngineRunner per
OODT-496)
- lifecycle status messages make sense
- fix unit tests to pass with changes to workflow Insts and Priorities, etc.
- in-mem cacheWPs (TODO: delete WPs when they are done likely per OODT-496)
> Add nextState (determineNextState) function to WorkflowProcessor
> ----------------------------------------------------------------
>
> Key: OODT-495
> URL: https://issues.apache.org/jira/browse/OODT-495
> Project: OODT
> Issue Type: Sub-task
> Components: workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.5
>
>
> Add the function that performs state transitions in the WorkflowProcessor.
> This was handled before in wengine-branch by WorkflowListeners, and detecting
> ChangeType.STATE_CHANGE. I like the whole listener thing, but decide on
> whether or not we need it later. For the moment, I think we can solve the
> state change issue by simply having a nextState or determineNextState
> function that is implemented by default in WorkflowProcessor and then
> possibly overridden in the sub classes.
--
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
