-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
6.1 Release Sprint
When SessionStore#createBeanStore is called, it would be more logical to return the existing store if it was previously created and re-use it.
At the moment though, a new one will be created and will over-write the existing one.
steps to reproduce:
- go to Segments app
- edit any segment, detail sub-app will create several components that involve choosers (each of them will attempt to initialise chooser)
- close the sub-app, that will trigger an error claiming that no bean storage is registered for choosers (cause the book-keeping sees several attempts to create it, but only the last remains).
With the fix the above situation is handled by creating the bean storage once and re-using it for the sub-sequent initialisation requests.
Acceptance criteria