[MGNLUI-4798] UI post-mortem clean-up clears out the wrong bean store when browser page refreshed Created: 15/Nov/18  Updated: 19/Nov/18  Resolved: 16/Nov/18

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

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: 6.0_release
Remaining Estimate: Not Specified
Time Spent: Not Specified
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: 6.0 requisite
Sprint: Basel 160
Story Points: 2

 Description   

There are two aspects:

  • stale UI's are cleared out as a side effect when the re-loaded UI is created. We call {{ getBeanStore(UiContextReference.ofCurrentUi()).clear()}} -> which will clear out the new UI's bean store. Explicit UI reference should be used.
  • the refreshed UI apparently has the same embed ID as the old one and since the embed ID is used as unique identifier of the UI - again, the new UI will get cleared out. We should complement the embed ID with the ui ID (spinner for every Vaadin session).

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