internationlization in facelet seems not working well

[reubin haz]

I have a web app built by JSF2, with English and French versions of pages.
I created a wrapper.xhtml as the template page, defined header, content, and footer pages

Then I created a helper page that uses this wrapper as the template.

<ui:composition xmlns="http://www.w3.org/1999/xhtml"
   xmlns:ui="http://java.sun.com/jsf/facelets"
   template="/template/wrapper.xhtml">  
  
  	<ui:define name="header">
		<ui:include src="/template/headerForReportingHome.xhtml"/>     
  	</ui:define>
  	
  	<ui:define name="content">
		<ui:include src="#{msgs.glossaryLink}"/>     
  	</ui:define>
</ui:composition>

'msgs.glossaryLink' contains the links for helper pages for English and French, which points to 2 different pages in different path

If I clicks from other page to come to this help page, it's loaded fine. But when I clicks the link for switching language link (in the header) in this helper page alone, the content portion, which is the file for English or French, is loaded one step behind, or I have to refresh the page in order for the content to match the header's locale.

Does this mean I cannot do internationlization in the facelet itself, or what's wrong with this behavior?

Thanks.

[Ilari Moilanen]

Can we see how you change the locale? Maybe there is something wrong in your code? Remember that you have to change the locale both locally (page level) and globally (in facescontext) in order to have the change take effect immediately. I know that it is a pain in the ass to change the locale in JSF and I have myself accomplished in doing it by following an example (do not remember the name of the book I read it from). Read for example this thread:
https://coderanch.com/t/515506/JSF/java/problems-JSF

[reubin haz]

Here is the code for the locale class

public class LocaleChanger implements Serializable { 
  private static final long serialVersionUID = 1L; 
  private boolean isEnglish = true; 
  
  HttpSession session = (HttpSession) FacesContext.getCurrentInstance().getExternalContext().getSession(true);
  
  public void swapLocale(ActionEvent event) {
	  
    switchLocale();
  }
  
  private void switchLocale() {
	getLocaleFromSession();  		  
	 
    isEnglish = !isEnglish;
    Locale newLocale;
    String languageTxt = "en";
    if (isEnglish) {
      newLocale = Locale.CANADA;
    } else {
      newLocale = Locale.CANADA_FRENCH;
      languageTxt = "fr";
    }
    FacesContext.getCurrentInstance().getViewRoot().setLocale(newLocale);
    session.setAttribute("isEnglish", isEnglish);
    
    if (SecurityContextHolder.getContext().getAuthentication().getPrincipal()instanceof AllUserDetails) {
      AllUserDetails springUser = (AllUserDetails) SecurityContextHolder.getContext().getAuthentication().getPrincipal();
      springUser.setLocale(newLocale);
      springUser.setLanguage(languageTxt);     
    }
  }

  public Locale getLocale() {
	getLocaleFromSession();  	  
	  
    if (isEnglish) {
      return(Locale.CANADA);
    } else {
      return(Locale.CANADA_FRENCH);
    }
  }  
  
  private void getLocaleFromSession() {
	if(session.getAttribute("isEnglish")!=null)
		isEnglish = (Boolean)session.getAttribute("isEnglish");
	else {  // set default locale
		isEnglish = true;
		session.setAttribute("isEnglish", isEnglish);
	} 
  }

}

The code is working for the header portion, not the content portion which is below it and specified by
<ui:define name="content">
<ui:include src="#{msgs.glossaryLink}"/>
</ui:define>

where #{msgs.glossaryLink} is either glossaryLink=/template/static/glossary/glossary.html or glossaryLink=/template/static_fr/glossary/glossary.html

Thanks

[Ilari Moilanen]

Your problem is such a specific one that it might just be that there is a bug in the implementation you use...

But just to make sure that you have set everything correct do you have f:view inside your wrapper.xhtml that is defined similar to this?

<f:view locale="#{localeChanger.locale}">
    <ui:insert name="header"></ui:insert>
    <ui:insert name="content"></ui:insert>
</f:view>

[reubin haz]

Yes, I have that in the wrapper page.
Actually I have other pages working for the content that contains #{msgs.key} inside content. But it's not working for the key as part of <ui:define name="content"> itself as I stated above. So I was wondering if facelet itself would have some problem?