deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] [Resolved] (DELTASPIKE-230) Fallback stragtegy for resource bundles and locales
Date Sun, 08 Jul 2012 12:36:34 GMT


Mark Struberg resolved DELTASPIKE-230.

       Resolution: Not A Problem
    Fix Version/s: 0.3-incubating

This can already be done by providing a simple MessageResolver as @Alternative. 

The DefaultMessageResolver relies on java.util.ResourceBundle and the mechanics defined therein.
> Fallback stragtegy for resource bundles and locales
> ---------------------------------------------------
>                 Key: DELTASPIKE-230
>                 URL:
>             Project: DeltaSpike
>          Issue Type: New Feature
>          Components: I18n-Module
>    Affects Versions: 0.2-incubating
>            Reporter: Thomas Herzog
>            Assignee: Mark Struberg
>             Fix For: 0.3-incubating
> Maybe it would be nice to have an fallback strategy for the resolving of the resource
bundles for given locale.
> For those usecases where the locale cannot be modified to an supported locale an fallback
strategy would be fine.
> If resources bundle with is present but Locale would be LANGUAGE_COUNTRY
or LANGUAGE_COUNTRY_VARIANT it would result in an Exception because resource bundles for these
kinds of Locales wouldn't be defined.
> It would be sensless to define resource bundles for all kind of possible locales such
as de_DE, de_AT, de_CH, maybe just in some special cases. Cal10N didn't provided this feature,
but i think if would be fine if deltaspike could. For sure this behavior should be enable
and disable able via @MessageContextConfig.
> Another question: 
> Does message module support merging of resource bundles such as cal10n does?
> Means resouce bundles with, are handled as a single
one in cal10n and if key is not present in but Locale is de_DE it takes the
one defined in

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message