[MGNLUI-5248] SessionStore does not re-use the existing bean storage when asked to create one Created: 14/Jun/19  Updated: 17/Jun/19  Resolved: 17/Jun/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.85h
Time Spent: 32m
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: UI framework implementation
Sprint: 6.1 Release Sprint

 Description   

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.


Generated at Mon Feb 12 09:24:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.