[MAGNOLIA-7561] ContextLocaleProvider gets hard-wired to a single context instance Created: 24/Jun/19  Updated: 24/Jun/19  Resolved: 24/Jun/19

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1

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

Issue Links:
Cloners
is cloned by MAGNOLIA-7562 CLONE - ContextLocaleProvider gets ha... Accepted
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: 6.1 Release Sprint

 Description   

Since the lifecycle of the ContextLocaleProvider is inknown - it should be careful about how it interacts with the mgnl context.

At the moment ctx locale provider merely injects the context instance and if context changes while the locale provider is alive - the wrong locale might be resolved.

A simple solution to this is to inject ctx provider into locale provider.


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