Yep, that's the idea. -- Adam
On 10/23/06, Gabrielle Crawford <[EMAIL PROTECTED]> wrote:
+1 for a formatting locale. If I'm understanding you correctly the formatting locale would only be used for formatting, meaning 11-7-06 in the US and 7-11-06 in Germany, but the error string will still use the regular locale... Thanks, Gab Adam Winer wrote: > JSF currently has support for one Locale, off of > FacesContext.getLocale(). > > It's also possible to override the locale on a per-converter basis by > explicitly setting the "locale" attribute on various converters. > This is useful for cases when you have, for example, only translations > into a limited set of languages (for example, just American English), but > need to show users dates formatted in the user's locale so > there is no accidental misinterpretation of dates (e.g., British > English or German). I've gotten some internal requirements for > using this functionality, but setting it on every single converter > gets to be painful. > > To make this easier, I'd like to expose a new Locale on RequestContext: > > Locale RequestContext.getFormattingLocale() > void RequestContext.setFormattingLocale(Locale locale) > > ... and have the DateTimeConverter and NumberConverter overrides > that Trinidad supplies automatically default to the formatting locale > if it is set to a non-null value. > > Comments? > > -- Adam
