I see that the problem is also related to the .properties file name. Java's Locale code (lowercase) such as: en_gb But the Locale automatically generated by Netbeans is lowercase_uppercase, for example: messages_en_GB.properties Change it to: messages_en_gb.properties Then it should work fine - if you've tried everything

You need to store the selected locale in session scope and set it in two places: once viaUIViewRoot#setLocale()Immediately after changing the locale (This will change the locale of the current view root so that it is reflected in subsequent requests; if you perform a redirect later, this part is unnecessary), and once inin thelocaleattribute (this will set/preserve the locale on subsequent requests/views).

Here is an example of howLocaleBeanshould look:

package com.example.faces; import java.util.Locale; import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; import javax.faces.context.FacesContext; @ManagedBean @SessionScoped public class LocaleBean { private Locale locale; @PostConstruct public void init() { locale = FacesContext.getCurrentInstance().getExternalContext().getRequestLocale(); } public Locale getLocale() { return locale; } public String getLanguage() { return locale.getLanguage(); } public void setLanguage(String language) { locale = new Locale(language); FacesContext.getCurrentInstance().getViewRoot().setLocale(locale); } }

This is an example of how the view should look:

This assumes that#{text}has been configured infaces-config.xmlas follows:

  com.example.i18n.text text  

Please note thatis not required for JSF functionality, but is mandatory for search engine explanation pages. Otherwise, it may be marked as duplicate content, which is bad for SEO.

See also:

• Maven and JSF web application structure, where are JSF resources placed?
• Internationalization in JSF, when to use message-bundle and resource-bundle?
• Internationalization of properties files using UTF-8 encoding in JSF 2.0 applications