-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
The current implementation of ContextLocaleProvider retrieves the Locale by calling the static MgnlContext.getLocale() method. This can cause issues when e.g translating notifications sent from a thread without MgnlContext set, e.g. triggered by JCR-Observation. (currently fails with IllegalStateException in MgnlContext.getInstance)
Anything that gets a SimpleTranslator through injection (i.e which injects a LocaleProvider indirectly) will currently be using the Locale of whatever context is bound to thread where it tries to do the translation.
If we injected the Context in ContextLocaleProvider instead, it'd be using the Locale corresponding to the context/thread where it was instantiated.
- is causing
-
MGNLSCH-56 Inject a Provider<SimpleTranslator> in CommandJob so that getting the Locale is deferred until the job is executed
- Closed
- is depended upon by
-
MGNLDAM-612 ImportAssetZipCommand can't be reinstantiated by N2B
- Closed
-
MGNLUI-3684 CLONE - ImportZipCommand can't be reinstantiated by N2B
- Closed
-
MGNLSLOCK-32 Port soft locking module to 5.0
- Closed
- is related to
-
MGNLUI-3458 Backwards compatibility in DialogDefinitionRegistry and providers
- Closed