-
Improvement
-
Resolution: Fixed
-
Neutral
-
5.2.2
-
None
-
None
-
-
Empty show more show less
-
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.
- depends upon
-
MAGNOLIA-7031 Allow injectable component configuration to be mapped via com.google.inject.Key instead of just Class
- Closed
- is causing
-
MGNLUI-4236 VaadinSession is not properly shared between several browser tabs (i.e. AdmincentralUI instances)
- Closed
-
MGNLUI-4275 Default sub-app's component bindings should be exposed to content app choose dialog component provider
- Closed
-
CONTEDIT-113 Adapt to UI IoC changes
- Closed
-
MGNLPN-386 Adapt trait chooser to changes in UI IoC
- Closed
- relates to
-
MGNLUI-4237 Make messages and task dispatchers queue the ui update via Vaadin UI object
- Closed
-
MGNLUI-4204 Integrate IoC improvements
- Closed
- mentioned in
-
Page Loading...
- Wiki Page
-
Wiki Page Loading...