[MAGNOLIA-6556] TranslationService could be started on ModulesStartedEvent Created: 19/Feb/16  Updated: 18/Jul/16  Resolved: 29/Feb/16

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

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2h 10m
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLGROOVY-143 Rescue app is broken due to i18n not ... Closed
is causing MAGNOLIA-6721 Translation service throws NPE if it'... Closed
is causing BLOSSOM-237 Adapt to new API in 5.4.7 Closed
dependency
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)
Sprint: Kromeriz 32
Story Points: 2

 Description   

TranslationService currently loads message bundles upon first translation. This is the case after adding support for origin since we can't start before the origin is started. With the introduction of ModulesStartedEvent, we can do that when all modules are started.
This is cleaner than the current solution which could unnecessary trigger i18n startup multiple times.


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