Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4180

Conduct UI-related IoC binding without Guice machinery ending up in the http session

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.5.5
    • 5.2.2
    • None
    • None
    • Yes
    • Basel 90, Basel 91, Basel 92, Basel 93, Basel 94
    • 21

      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.

        Acceptance criteria

              apchelintcev Aleksandr Pchelintcev
              apchelintcev Aleksandr Pchelintcev
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD