That might be the idea, but doesn't work either. It's always overriden
by ServletWebRequest.getLocale, which in case it can't make up the
locale from the request header, defaults to the server's locale -
which is not the locale that is set as the default for Wicket.
Eelco
On 5/11/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
no, the default locale is used when we cannot figure out what the user's
local is afaik. since the browser is sending a locale that will be used.
-Igor
On 5/11/06, Bruno Borges <[EMAIL PROTECTED]> wrote:
>
> Shouldn't these calls override any locale the user is sending at the
request (from the browser)?
>
> getApplicationSettings().setDefaultLocale(new
Locale("pt", "BR"));
> getResourceSettings().setDefaultLocale(new
Locale("pt", "BR"));
>
> I still get english messages, that comes from Application.properties. My
tought was that, overriding the default locale, I would get portuguese
messages.
>
> Regards
>
>
> --
> Bruno Borges
> [EMAIL PROTECTED]
> Sun Certified Java Programmer for 1.4
> Sun Certified Web Component Developer for 1.4
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
