Thanks for your reply. I'm using WebLogic 9.2. I'd tell you how the login.jsp is localized, but I haven't been able to figure it out yet. I don't see anything on the page that I'd associate with i18n except that
1. It's already calling tiles custom tags, and 2. There are fmt:message tags on the page too, so it clearly has something localized before it loads. I'll see if I can get any help from the dev2dev forums at WebLogic -- thanks again for your help! Chris -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper Sent: Monday, February 11, 2008 3:49 PM To: user@struts.apache.org Subject: Re: [probably OT] Default locale on login page Christopher Loschen wrote: > Hi all, > > My best guess is that this is happening before Struts gets involved, but > I wondered if anyone might have some suggestions or places for me to > look. I'm having some strange i18n behavior on our initial login page. > > Our app is still using Struts 1.1 (don't ask..). We're using form-based > authentication through WebLogic, set up pretty much plain vanilla from > what I can tell (from the web.xml): > > <login-config> > <auth-method>FORM</auth-method> > <form-login-config> > <form-login-page>/login.jsp</form-login-page> > <form-error-page>/login_error.jsp</form-error-page> > </form-login-config> > </login-config> > > User gets redirected to the login page, it appears, before the Struts > actions are called at all, because I can't seem to find anyplace to put > a breakpoint in my debugger. Right; the container sees that the request is not authenticated and transfers control to the login page before allowing any 'normal' request processing to occur. > The problem is that when I have more than one locale defined in my > browser preferences (either in IE or FF), it doesn't take the default > first choice (which is en_us) but one of the others instead. I don't > have the same problem on other internationalized web sites, so I presume > it's a problem in my code or configuration or something, but I'm not > sure where to start looking. Oh, by the way, once the user logs in, > there are user preferences for locale which kick in, but those obviously > don't apply to this page because there's no user in the session as of > yet, so it has to be getting the locale from the browser preferences. You don't describe how you have localized your login page so it's impossible to offer very specific advice. However, since this the login page is effectively outside of Struts, any locale selection logic must also be outside of Struts. In other words, you're dealing with standard HTTP Servlet behaviour. That said, I'm not sure exactly how 'standard' that behaviour is; it may be container dependent. Therefore, I'd recommend asking on the support forums or mailing lists for whatever servlet container you're using (Tomcat?) L. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
