Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancing ResourceBundleMessageSource to Support Multiple Message Files in Micronaut #10974

Open
rsalbergaria opened this issue Jul 11, 2024 · 0 comments
Labels
info: good first issue Good for newcomers status: under consideration The issue is being considered, but has not been accepted yet

Comments

@rsalbergaria
Copy link

rsalbergaria commented Jul 11, 2024

We are currently in the process of migrating our Java workloads from Spring to Micronaut. During this transition, some of our teams that previously used Spring have raised concerns regarding the behavior of the ResourceBundleMessageSource in Micronaut, specifically in how it handles resource message files.

In our Spring setup, we have a common practice of utilizing message files from both a shared library and individual microservices. This allows us to aggregate messages from both sources, effectively treating the resource bundle reading as a list. However, we've noticed that in Micronaut, ResourceBundleMessageSource seems to be limited to loading only one bundle by its name, which poses a challenge to our current approach.

Given this context, we are interested in exploring the possibility of enhancing the ResourceBundleMessageSource in Micronaut to support the aggregation of messages from multiple files, similar to our existing setup in Spring. This feature would greatly facilitate our migration efforts and ensure consistency in how we manage our internationalization resources across our services.

@graemerocher graemerocher added info: good first issue Good for newcomers status: under consideration The issue is being considered, but has not been accepted yet labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info: good first issue Good for newcomers status: under consideration The issue is being considered, but has not been accepted yet
Projects
None yet
Development

No branches or pull requests

2 participants