deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] [Commented] (DELTASPIKE-229) Add JSFLocaleResolver as an DeaultLocaleResolver
Date Sat, 07 Jul 2012 19:27:33 GMT


Mark Struberg commented on DELTASPIKE-229:

that will be part of the JSF module. If present, it will @Specialize the DefaultLocaleResolver
> Add JSFLocaleResolver as an DeaultLocaleResolver
> ------------------------------------------------
>                 Key: DELTASPIKE-229
>                 URL:
>             Project: DeltaSpike
>          Issue Type: New Feature
>          Components: I18n-Module
>    Affects Versions: 0.2-incubating
>            Reporter: Thomas Herzog
>             Fix For: 0.4-incubating
> Add an JSFLocaleResolver which should get the Locale out of the view root.
> For messages used in views this would be fine if delta spike would provide it out of
the box.
> I know not that much code to write, but still a class more in the source, for a code
which nearly every web developer will use, i think.
> This is my opinion, because we set the locale via <f:view locale="#{localeBean.viewLocale}"
/> in every view, because we do provide resouce bundles for de_DE, en_US, ... an not for
de_AT or de_CH and if we wouldn't do it that way, the request locale would used, and this
would result in an MessageBundleNotFoundException. 
> We tried to put the locale in the view root via PhaseListener before, but sometimes EL
got evaluated before.
> What you think?
> Do developer get the locale for messages via the view root as we do, or do they get the
locale in an different way?

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