Announcement Announcement Module
No announcement yet.
Change Locale Page Title Module
Move Remove Collapse
This topic is closed
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Change Locale

    I am trying to make our webapp I18N compatible but we want our users to be able to "choose" their locale. The way we are doing this is on the login.jsp page there are links to a set list of available languages. When they click on the appropriate link it changes their locale through Springs SessionLocaleResolver and a LocaleChangeInterceptor.

    <bean id="localeChangeInterceptor" class="org.springframework.web.servlet.i18n.LocaleChangeInterceptor">
         <property name="paramName" value="siteLang" />
    <bean id="localeResolver" class="org.springframework.web.servlet.i18n.SessionLocaleResolver" />
    <!-- Map urls to controller -->
    <bean id="beanNameUrlMapping" class="org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping">
         <property name="interceptors">
                   <ref bean="localeChangeInterceptor" />
         <property name="order"><value>0</value></property>
    I've got this part of the code working fine but now I'm looking for the best way to make this work with Acegi. I'm using a custom authenticationDao but I'm using Acegi's DaoAuthenticationProvider.

    Here's my filter chain proxy setup:
    <bean id="filterChainProxy" class="net.sf.acegisecurity.util.FilterChainProxy">
          <property name="filterInvocationDefinitionSource">
    NOTE:lanchange.html just points to a simple controller I wanted outside the security wall to change the locale FROM the login.jsp page. It's currently called from a second form on the login.jsp page that calls /langChange.html?siteLang="<de,en,etc>". But my actual login form on login.jsp calls /j_acegi_security_check. What I think I want to do is add this siteLang input to the /j_acegi_security_check form and have it get processed by the SessionLocaleResolver.

    I've come up with some possible approaches but none of them sound like they'll work:

    1.The way the SessionLocaleResolver works is that whenever I make a request that is processed through Spring's UrlHandlerMapping, an interceptor on that handler (see code above) looks for a request parameter called "siteLang". If it finds it, it changes the locale to the value of siteLang. I figured I can just add another input to my login.jsp page called "siteLang" and submit it along with the rest of the fields. The problem is that I can't put "j_acegi_security_check" into my Spring urlHandlerMapping bean can I? If I can, where do I have it map to?

    2.Maybe I can just pass "siteLang" input from login.jsp just as another input and write my own implementation of some Acegi class in the authentication process that manually calls RequestContextUtils.getLocaleResolver(request).set Locale(request,response,new Locale("en,de,etc"));.

    I'm not sure if either of these will work however. Any advice would be helpful.

    Maybe I'm making this much more complicated than it needs to be. In short my goal is that I want to give our users the ability to choose their language from the Login page. I want to use the Locale for this because we're using Springs ResourceBundleViewResolver with I18N based interntionalization. But I don't want to just use their browser's locale, I want the user to choose one from the login screen, so I need to use one of Spring's locale resolvers. I'd like to have it be the SessionLocaleResolver but I'm flexible on that. I know how to do all of this outside of Acegi, but now I need to integrate it with the Acegi login process. If anyone has a nice clean way to do this I'd be in your debt. This has been driving me nuts.

  • #2
    Figured it out

    My apologies for the long question. I had one of those random brainstorms. I'm not sure if this is the "right" way to do this but it works quite well.

    I created a subclass of AuthenticationProcessingFilter and overrode the onSuccessfulAuthentication() method. In this method I just call the super class version of this method followed by logic to create a SessionLocaleResolver and set the session locale using the siteLang input parameter I pass it through the form. Each subsequent request in the application (after logging in) shows the correct locale we were looking for.

    Sorry if my post wasted anyone's time. Thanks for reading though.


    • #3
      Internationalization has been added as per