You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/05/04 16:12:03 UTC
[jira] [Resolved] (OODT-189) Refactor and clean up
WorkflowCondition Configuration
[ https://issues.apache.org/jira/browse/OODT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-189.
------------------------------------
Resolution: Fixed
- fixed in r1099455.
> Refactor and clean up WorkflowCondition Configuration
> -----------------------------------------------------
>
> Key: OODT-189
> URL: https://issues.apache.org/jira/browse/OODT-189
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
> Affects Versions: 0.1-incubating, 0.2
> Environment: while working on OODT-156
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: condition, config, refactoring, workflow
> Fix For: 0.3
>
>
> I noticed while working on OODT-156, I noticed that in the {code}WorkflowConditionConfiguration{code} class, I noticed some areas for refactoring improvement:
> * there is a method #getTaskConfig (this should be #getCondConfig) - I am going to deprecate #getTaskConfig, leave it, and add the more natural #getCondConfig.
> * the default WorkflowCondition constructor doesn't create a new WorkflowConditionConfig -- neither does the parameter-based one. This should be fixed, else you always have to create a blank config and set it which is a pain.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira