JBossDeveloper

Hi,

that's strange. What do you mean with "through the browser"? Does it mean through the application UI (e.g. using something like <h:commandButton action="#{localeSelector.selectLanguage('en')}" />) or configuring browser settings (HTTP Accept-Language header)? Anyways I did some basic tests and still cannot reproduce...

Hm, that's really odd. I did some more tests (emulating browser and HTTP header settings) and the only way to get the message key (missing resource bundle) was to supply Accept-Language header with locale that was not listed in the supported locales in faces-config.xml (JSF falls back to the default locale of the server) and having no messages for the server default locale... However if I supply the default messages.properties file it logically works (if I remember correctly you have the default messages file, do you?). So I think we're stuck. At least you have the working workaround...

I have no idea. Init is a Seam component that holds configuration settings. I guess it might cause the problem if you have more than one web archives using Seam in your EAR...

Hi Bram, did you ever get to the bottom of this?

I have the same problem with Resource Bundle getting dropped when I change Locale manually (it just shows the message keys), no errors are thrown so I think it may be a config issue?

Regards

David

Hi Bram,

Thanks for the update, I have tried your method, doing a redirect after the localeSelector.select() action, but my problem still persists, its annoying that sometimes when I restart the server I can switch between message bundles ok, but on other times, when I change language it just loads the message keys

I am trying to figure out a way to debug the ResourceBundle loader to see why the new bundle is not loading correctly, if you have any advice it would help!

Regards

David

Thank you sir! Yes thats exactly what I needed (I am on 2.2.2.Final)

After implementing your custom resource loader the problem has dissapeared. Funny because I was getting the MissingResourceException (even though the Message bundle did load) successfully)

I did some experimenting and it looks like the...

java.util.ResourceBundle.clearCache();

...is the silver bullet, as long as this is being called the new MessageBundle loads ok (I will test in production tomorrow)

Im not sure if this is a bug in SEAM or I am doing something wrong, my change language method looks like this...

@Override

public String updateLanguage(String newLocaleString){

     String currentLanguage = localeSelector.getLocaleString();

     if(!newLocaleString.equalsIgnoreCase(currentLanguage)){

          localeSelector.setLocaleString(newLocaleString);

          localeSelector.select();

          messagePoster.postPopupInfoEntityMessage("entityUpdated","entity.language",1);

     }

     return Page.index.getPath();

}

Hi

I have exactly the same problem as You (lost internationalization, keys displayed instead), and I can reproduce the problem under any browser.

1. Environment

Seam 2.2.0.GA with RichFaces 3.3.1.GA under JBoss 5.1.0.GA. Application is deployed as EAR file and uses stateless session beans (EJB3) internally.

2. Description.

I have a simple login page (login.xhtml) which displays login and password field and drop-down field with so called "departments" of the company where user is trying to log in. Departments are stored in database and mapped to the entity class named Department.java. A list of Departments is loaded from database by special SLSB (DictionaryService.java) and is used to create a list of SelectItem to display mentioned drop-down list on login.xhtml page. Loading is done when user enters the login.xhtml page with the help of Seam "page action" defined in pages.xml. Localized depratments names in the drop-down list are taken from messages.properties files (a key is stored in database and is returned in Department.java entity). Here is the complete code (trimmed for clarity):

<?xml version="1.0" encoding="UTF-8"?>
<pages ...>
  <page view-id="/login.xhtml" login-required="false" action="#{userContext.prepareDepartmentsToSelect}">
</pages>

<?xml version='1.0' encoding='UTF-8'?>
<faces-config ...>
  <locale-config>
  <default-locale>pl</default-locale>
  <supported-locale>pl</supported-locale>
  <supported-locale>en</supported-locale>
  </locale-config>
</faces-config>

@Name(UserContext.NAME)
@Scope(ScopeType.SESSION)
public class UserContext {
    public static final String NAME = "userContext";
    @In (create = true)
    DictionaryService dictionaryService;
    private List<SelectItem> departmentsToSelect;


    public void prepareDepartmentsToSelect() {
        departmentsToSelect = new ArrayList<SelectItem>();
        List<Department> departments = dictionaryService.loadDepartments();
        for (Department dep: departments) {
            departmentsToSelect.add(new SelectItem(dep, dep.getNameToDisplay()));
        }
    }
...
}

@Local
public interface DictionaryService {
  public static final String NAME = "dictionaryService";
    public List<Department> loadDepartments();
}

@Stateless
@Name(DictionaryService.NAME)
public class DictionaryServiceBean implements DictionaryService {
    @PersistenceContext
    private EntityManager em;
    @Override
    public List<Department> loadDepartments() {
        Query queryDep = em.createQuery("select dep from Department dep");
        List<Department> departments = queryDep.getResultList();
        // set name to be displayed on GUI
        SeamResourceBundle seamResourceBundle = (SeamResourceBundle) Component.getInstance("org.jboss.seam.core.resourceBundle");
        for (Department dep: departments) {
            try {
                String localizedName = seamResourceBundle.getString(dep.getLocalizedNameKey());
                dep.setNameToDisplay(localizedName);
            } catch (MissingResourceException mre) {
                dep.setNameToDisplay("## "+dep.getLocalizedNameKey()+" ##");
            }
        }
        return departments;
    }
}

3. Error

In the above method loadDepartments() I use Seam component for resources to obtain a real name for the key stored in Department entity (database). And now: if I start the server and I am trying to display the login page (login.xhtml), my internationalization is broken. I see keys instead of proper messages, not only on drop-down list but also on other login.xhtml page elements which uses internationalization, i.e. <h:commandButton value="#{messages['general.login']}" action="#{userContext.loginUser}" />. Other pages in the application are also broken. To be precise: MissingResourceException is thrown in the loadDepartments() method.

4. Reason and workaround

I figured out that the problemin my case is connected with using SeamResourceBundle inside SLSB as a first action in application after server startup. If I move code reposnsible for resolving localized named higher, into the UserContext component, then restart server and invoke login.xhtml, everything WORKS OK:

@Name(UserContext.NAME)
@Scope(ScopeType.SESSION)
public class UserContext {
    public static final String NAME = "userContext";
    @In (create = true)
    DictionaryService dictionaryService;
    private List<SelectItem> departmentsToSelect;
    public void prepareDepartmentsToSelect() {
        departmentsToSelect = new ArrayList<SelectItem>();
        List<Department> departments = dictionaryService.loadDepartments();
        // resolving localized name moved from SLSB
        SeamResourceBundle seamResourceBundle = (SeamResourceBundle) Component.getInstance("org.jboss.seam.core.resourceBundle");
        for (Department dep: departments) {
            try {
                String localizedName = seamResourceBundle.getString(dep.getLocalizedNameKey());
                dep.setNameToDisplay(localizedName);
            } catch (MissingResourceException mre) {
                dep.setNameToDisplay("## "+dep.getLocalizedNameKey()+" ##");
            }
            departmentsToSelect.add(new SelectItem(dep, dep.getNameToDisplay()));
        }
  }
...
}

Moreover, if I display some dummy page after the server startup, and this page displays dummy text from messages.properties (i.e. <h:outputText value="#{messages['some.key']}"/>) and as NEXT I will invoke login.xhtml, everything works OK regardless of a place where I use SeamResourceBundle (in UserContext or in SLSB)

So a workaround will be displaying some dummy page or manually invoke SeamResourceBundle.getString() "higher" than in SLSB. The browser and its language setting has nothing to do with that (I tested it with Chrome, IE, FF). Hope this helps someone.

Regards,

Pawo509