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 2010/12/07 08:19:11 UTC

[jira] Created: (OODT-71) Add lifecycle model supporting transition, done and waiting states

Add lifecycle model supporting transition, done and waiting states
------------------------------------------------------------------

                 Key: OODT-71
                 URL: https://issues.apache.org/jira/browse/OODT-71
             Project: OODT
          Issue Type: Improvement
          Components: workflow manager
         Environment: indep. of env.
            Reporter: Chris A. Mattmann
            Assignee: Chris A. Mattmann
             Fix For: 0.2


We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:

# done/
# holding/
# initial/
# results/
# running/
# transition/
# waiting/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (OODT-71) Add lifecycle model supporting transition, done and waiting states

Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ramirez updated OODT-71:
-----------------------------

    Fix Version/s:     (was: 0.2)
                   0.3

Pushing off to 0.3 release.

> Add lifecycle model supporting transition, done and waiting states
> ------------------------------------------------------------------
>
>                 Key: OODT-71
>                 URL: https://issues.apache.org/jira/browse/OODT-71
>             Project: OODT
>          Issue Type: Improvement
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.3
>
>
> We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:
> # done/
> # holding/
> # initial/
> # results/
> # running/
> # transition/
> # waiting/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] [Updated] (OODT-71) Add lifecycle model supporting transition, done and waiting states

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Fix Version/s:     (was: 0.3)
                   0.4

push to 0.4

> Add lifecycle model supporting transition, done and waiting states
> ------------------------------------------------------------------
>
>                 Key: OODT-71
>                 URL: https://issues.apache.org/jira/browse/OODT-71
>             Project: OODT
>          Issue Type: Improvement
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:
> # done/
> # holding/
> # initial/
> # results/
> # running/
> # transition/
> # waiting/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OODT-71) Add lifecycle model supporting transition, done and waiting states

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Issue Type: Sub-task  (was: Improvement)
        Parent: OODT-215

> Add lifecycle model supporting transition, done and waiting states
> ------------------------------------------------------------------
>
>                 Key: OODT-71
>                 URL: https://issues.apache.org/jira/browse/OODT-71
>             Project: OODT
>          Issue Type: Sub-task
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:
> # done/
> # holding/
> # initial/
> # results/
> # running/
> # transition/
> # waiting/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OODT-71) Add lifecycle model supporting transition, done and waiting states

Posted by "Chris A. Mattmann (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-71.
-----------------------------------

    Resolution: Fixed

- fixed in r1301857.
                
> Add lifecycle model supporting transition, done and waiting states
> ------------------------------------------------------------------
>
>                 Key: OODT-71
>                 URL: https://issues.apache.org/jira/browse/OODT-71
>             Project: OODT
>          Issue Type: Sub-task
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:
> # done/
> # holding/
> # initial/
> # results/
> # running/
> # transition/
> # waiting/

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

        

[jira] [Commented] (OODT-71) Add lifecycle model supporting transition, done and waiting states

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OODT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082173#comment-13082173 ] 

Chris A. Mattmann commented on OODT-71:
---------------------------------------

Going to start on this tomorrow.

> Add lifecycle model supporting transition, done and waiting states
> ------------------------------------------------------------------
>
>                 Key: OODT-71
>                 URL: https://issues.apache.org/jira/browse/OODT-71
>             Project: OODT
>          Issue Type: Sub-task
>          Components: workflow manager
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> We've been experimenting with some new state models in our internal workflow testing at JPL. It would be nice to flow some of those state models in an explicit o.a.oodt.cas.workflow.lifecycle workflow model package. Something like the following might make sense:
> # done/
> # holding/
> # initial/
> # results/
> # running/
> # transition/
> # waiting/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira