[
https://issues.apache.org/jira/browse/OODT-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026727#comment-14026727
]
Chris A. Mattmann commented on OODT-593:
----------------------------------------
in r1601694, I fixed some other stuff with this:
* in OPSUI, if you clicked on the workflow model for a dyn workflow from the
status page, it would crash, as it couldn't find the model since it wasn't part
of the repo (added caching of the dyn model on the first time it's loaded, so
future calls will return this)
* also added support in #WorkflowRepository#add for allowing the passed in ID
if the workflow model already has one to take precedence and not be reset by
the UUID generator. This allows existing dyn workflow IDs to be used to
retrieve workflow models
OPSUI now fully supports dynWorkflows.
> Dyn workflows in Workflow Manager cause NPEs on restart
> -------------------------------------------------------
>
> Key: OODT-593
> URL: https://issues.apache.org/jira/browse/OODT-593
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
> Affects Versions: 0.5
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Critical
> Fix For: 0.7
>
> Attachments: OODT-593.Mattmann.060914.patch.txt,
> OODT-593.Mattmann.061014.patch.txt
>
>
> Since dyn workflows showed up in OODT 0.5 (OODT-209), dynamic models aren't
> persisted to the WM repo, and thus aren't loadable after restarting the WM.
> We need to:
> * check to see if the model can't be found, if not; then
> * look it up from the instance repo (b/c we likely have cached it)
> That should do the trick.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
