[MGNLUI-4256] App launcher layout update should be conducted in a thread safe manner and with MgnlContext provided Created: 17/Jul/17 Updated: 26/Jun/19 |
|
| Status: | Accepted |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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
|
||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Description |
|
When app definitions are tossed around, e.g. new apps created and existing apps removed (e.g. during LD sessions) - there might be exceptions thrown by UI engine claiming that the app layout re-organisation is failing due to the MgnlContext not being set during the operation. The user perceives the issue as broken App Launcher. This is caused by the fact that the registry update happens outside of the UI thread and we need to take standard measures to "synchronise" that operation with Vaadin lifecycle. We also need to ensure that the context is set (i.e. execute the operation in system context). |