Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Basel 157
-
2
Description
Currently the mentioned provider clashes sometimes with the providert of the mgnl context breaking the execution of some actions.
This happens due to imperfection of how the parameter resolvers pick the candidates for the c-tor injection (basically they do not distinguish between the two instances of javax.inject.Provider due to generic erasure at runtime). Ideally provider resolution should be delegated to GuiceParameterResolver, but UiContextParameterResolver can also look into the BeanStores that are used by Guice for scoping objects.
Sensible solution would be to forbid the UiContextParameterResolver to try to resolve an IoC provider instance (it is not meant for this type of objects anyway).
Checklists
Acceptance criteria