[MGNLUI-4237] Make messages and task dispatchers queue the ui update via Vaadin UI object Created: 04/Jul/17  Updated: 10/Jul/17  Resolved: 04/Jul/17

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

Type: Bug Priority: Blocker
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-4236 VaadinSession is not properly shared ... Closed
relates to MGNLUI-4180 Conduct UI-related IoC binding withou... Closed
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
Sprint: Basel 103
Story Points: 3

 Description   

When task and message dispatchers dispatch the events, we trigger somewhat complex sequences of operations that eventually update Pulse tables. Several steps include dependency injection which as of MGNLUI-4180 requires Vaadin UI threadlocal to be set to the correct instance. Unfortunately in the current impl of the dispatchers, we queue the event propagations via VaadinSession#access(..) which doesn't provide the UI instance correctly. Using UI.access(...) in turn provides the UI instance and is a more logically suitable for the task.


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