Workflow always refer to old bean id
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2011 03:50 PM
I have created Action class for workflow, I define the bean id as "test_wf".
In workflow definition xml, I have defined previous workflow:
Then I changed to:
When I publish the tree, it always complains old "orig_wf" action id which doesn't exists now. I re-start and clean temp and work directories in tomcat but still. I have no idea. Is it possible previous workflow definition cached somewhere?
Thanks
In workflow definition xml, I have defined previous workflow:
<transition name="approve" to="approved"> <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript"> <script> var publishAction = actions.create("orig_wf"); publishAction.execute(bpm_package); </script> </action> </transition>
Then I changed to:
<transition name="approve" to="approved"> <action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript"> <script> var publishAction = actions.create("test_wf"); publishAction.execute(bpm_package); </script> </action> </transition>
When I publish the tree, it always complains old "orig_wf" action id which doesn't exists now. I re-start and clean temp and work directories in tomcat but still. I have no idea. Is it possible previous workflow definition cached somewhere?
Thanks
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2011 05:16 PM
Yes workflow definitions are persisted into the JBPM database so existing in flight workflow instances may complete with the old definition.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2011 05:18 PM
Thanks. I did "undeploy definition name <workflowname>". It works.