[MGNLUI-4180] Conduct UI-related IoC binding without Guice machinery ending up in the http session Created: 30/Mar/17  Updated: 19/Dec/19  Resolved: 07/May/17

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

Type: Improvement Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-4237 Make messages and task dispatchers qu... Closed
relates to MGNLUI-4204 Integrate IoC improvements Closed
causality
is causing MGNLUI-4236 VaadinSession is not properly shared ... Closed
is causing MGNLUI-4275 Default sub-app's component bindings ... Closed
is causing CONTEDIT-113 Adapt to UI IoC changes Closed
is causing MGNLPN-386 Adapt trait chooser to changes in UI IoC Closed
dependency
depends upon MAGNOLIA-7031 Allow injectable component configurat... Closed
relation
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)
Release notes required:
Yes
Sprint: Basel 90, Basel 91, Basel 92, Basel 93, Basel 94
Story Points: 21

 Description   

UI-related IoC bindings should be done ideally once and should manipulate/utilise http and Vaadin sessions through custom Guice scopes rather then emulating such scopes via multiple Injector instances (see linked wiki entry for more details).

For the release notes:

  • All the UI related component bindings are now served by a single GuiceComponentProvider. Where before we were creating GuiceComponentProviders on demand (for apps, sub-apps etc), we now merely create a cheap ComponentProvider which delegates to the single one and sets its context.


 Comments   
Comment by Aleksandr Pchelintcev [ 07/May/17 ]

The effort has been approved during the architecture group discussion and has gotten a green light to be integrated. However, several additional steps have to be taken before this is possible, hence a follow-up ticket is created.

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