Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: framework-2.4.2
-
Fix Version/s: openengsb-3.0.0.M1
-
Component/s: framework
-
Labels:
Description
Workaround for this (in case someone else experiences this): Overwrite old Workflows at startup of your app (e.g. RuleManager.addOrUpdate() until this is fixed
Gliffy Diagrams
Gerrit Reviews Web Panel
Activity
I guess this should have been fixed when adding persistence to the rulemanager. I wont do an additional test since I am currently removing the Rulemanager 
Show
Lukas Stampf
added a comment - I guess this should have been fixed when adding persistence to the rulemanager. I wont do an additional test since I am currently removing the Rulemanager
to reproduce the bug create an app that adds a workflow to the openengsb (RuleManager.add(RuleBaseElementType.Process, WORKFLOW_ID)).
now you should be able to start the workflow with WorkflowService.startFlow(WORKFLOW_ID).
stop karaf.
start it again.
do a ruleManager.get(new RuleBaseElementId(RuleBaseElementType.Process, WORKFLOW_ID)).
it should still contain your workflow.
but WorkflowService.startFlow(WORKFLOW_ID) should fail.