Re: Best Practices for PrettyFaces and Multiple language sites

Splash Forums PrettyFaces Users Best Practices for PrettyFaces and Multiple language sites Re: Best Practices for PrettyFaces and Multiple language sites

#20694

icordoba
Participant

Hello,

The only reason for using a different xhtml was because I haven’t been able to find a way to map the pretty-config file so that spanish language is in / and english is in /en while having one unique h:link group for both (I mean, the links in the home spanish page don’t have the “language” parameter and the other languages in the site do have them). I anyway have decided to put spanish content also in a subdir (es) so this way I can use just one home page, so no big deal.

About your approach, that is exactly what I’ve done (the LocaleBean, which I named UserSessionView is @RequestScoped). What I meant is that most online tutorials about this seem to understand that locale info must be SessionScoped and not RequestScoped and so I had to recode my bean so the locale info is stored in the request.

Thanks again for your time. I now have my new site working with SEO i18n friendly JSF2 thanks to PrettyFaces.