JavaServer Faces 1.0 Early Access Draft (Page 6)

<< Page 5 (Validation and Error Messages)

Internationalization

Section JSF 5.1.2 covers the use of Locales with the FacesContext in order to support localization of UIComponents (and error messages, I'm assuming). This has a major impact on Internationalization. It seems as though it is impossible to render different UIComponents with different Locales. Multi-lingual applications will need this functionality.

Let's assume that you can Localize each UIComponent. When different UIComponents encode using different Locales and the HttpServletResponse's content type supports one locale but not another, there could be rendering problems on the client side in the browser.

Section JSF 5.1.5 talks about the Message classes and how error messages are added to the FacesContext. This section however forgets a major step in internationalization. Messages that are added to the message queue (during validation or processing) contain Unicode String Objects and therefore could be written in any language. The Message Object does not contain information about the Locale that the message needs to be converted to - and this is needed for internationalization.

It seems as though the specification wants to force all localization into the Locale set into the FacesContext, which as I've already mentioned can be detrimental. JSF, as it stands, does not seem to support error messages in multiple languages. The use of multiple languages is something that needs to be addressed and carefully considered because of the problems inherent to it (such as determining the encoding when two locales require different encodings).

>> Page 7 (Nice to have / Readability)

<< Back to Programming