Details
-
Bug
-
Resolution: Done
-
Major
-
2.1.0.CR2
-
None
-
None
Description
To reproduce the problem, start the server and console, and then follow these steps:
1) Go to samples/quickstarts/simple_correlation and run "ant deploy -Dversion=1"
2) Start first process instance using "ant sendhello"
At this point (after pressing Refresh button) you should be able to select the process definition (version 1) and see the process instance
3) Deploy second version using "ant deploy -Dversion=2"
4) Create second process instance using "ant sendhello2"
At this point, if you select (after another Refresh) the active process definition (version 2), then the new process instance will be displayed. However if you select the retired process instance, it still shows the latest process instance. It should show the process instance associated with version 1.
If you now select another tab (e.g. Runtime/Deployments) and then return to the Processes, and then select the Retired process definition (version 1), it does not show any process instances - so looks like if the active process definition is selected prior to selecting the retired version, then it just leaves the process instances uncleared.
So there appears to be two problems:
(1) Why is the active process instance associated with the retired process definition not being displayed (it is still active, as this can be confirmed by running "ant sendgoodbye")
(2) Why does the list of process instances associated with the retired process definition not have consistent behaviour, depending on whether it is selected before or after the active process definition.