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] [Resolved] (OODT-495) Add nextState (determineNextState) function to WorkflowProcessor
Date Wed, 27 Feb 2013 17:11:13 GMT

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

Chris A. Mattmann resolved OODT-495.
------------------------------------

    Resolution: Fixed

- OODT-491 close out: WorkflowProcessor#nextState has a stub implementation that is a good
enough start. More can be improved later.
                
> 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.6
>
>
> 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

Mime
View raw message