Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Date: Sun, 8 Jul 2012 12:36:34 +0000 (UTC)
From: "Mark Struberg (JIRA)" <jira@apache.org>
To: deltaspike-dev@incubator.apache.org
Message-ID: <1977959285.19977.1341750994924.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1230601385.19195.1341690754715.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Resolved] (DELTASPIKE-230) Fallback stragtegy for resource
 bundles and locales
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DELTASPIKE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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: https://issues.apache.org/jira/browse/DELTASPIKE-230
>             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 message_LANGUAGE.properties 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 _de.properties, _de_DE.properties are handled as a single one in cal10n and if key is not present in de_DE.properties but Locale is de_DE it takes the one defined in _de.properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira