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

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

    Description: 
The WorkflowProcessor class in reality is a control flow model. I've determined 
that is its ultimate intent after a thorough code review of wengine and my own 
views for the initial workflow effort. 

However, the class beyond classic control flow information replicates its own 
set of class-level attributes/properties that themselves are already somewhat 
duplicated if not explicitly, at least implicitly, by the WorkflowInstance 
class. 

This patch will leverage WorkflowInstance to store any currently running 
workflow information (as opposed to control flow information) inside of the 
WorkflowInstance attributes. 
    
> Refactor WorkflowProcessor to push all of its state information into Workflow 
> Instance
> --------------------------------------------------------------------------------------
>
>                 Key: OODT-490
>                 URL: https://issues.apache.org/jira/browse/OODT-490
>             Project: OODT
>          Issue Type: Bug
>          Components: workflow manager
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.5
>
>
> The WorkflowProcessor class in reality is a control flow model. I've 
> determined that is its ultimate intent after a thorough code review of 
> wengine and my own views for the initial workflow effort. 
> However, the class beyond classic control flow information replicates its own 
> set of class-level attributes/properties that themselves are already somewhat 
> duplicated if not explicitly, at least implicitly, by the WorkflowInstance 
> class. 
> This patch will leverage WorkflowInstance to store any currently running 
> workflow information (as opposed to control flow information) inside of the 
> WorkflowInstance attributes. 

--
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

Reply via email to