Sorry about the previous e-mail title... I was going to change before sending it and I forgot.
Well... here's the problem. I didn't explain it well before: - My app has 2 Supported Languages : 'pt-BR' (default) and 'en'. - By default, when the app is acessed with an Unlocalized URL (like http://localhost:8181/myapp/start), the framework will identify the Browser's language, and the current Locale for work will be 'pt-BR' (because of my browser's language) - When the user changes the current Language, every new URL will use the Locale prefix after the app context... Like http://localhost:8181/myapp/en/start - If I submit a request to an Unlocalized url - like http://localhost:8181/myapp/start - the framework will not use the stored Locale for work... So, the request will use the Default Locale ('pt-BR', in my case) There is any way I can change this behavior? We're having these problems because of a Code-Generation API that is being lost with some URL's creation. Thanks :) Everton Agner ________________________________ De: Everton Agner <everton_ag...@yahoo.com.br> Para: Tapestry Users <users@tapestry.apache.org> Enviadas: Terça-feira, 17 de Novembro de 2009 18:03:30 Assunto: Localization There is any way to call a i18n page without using a localized url? Sample: 1. User selected some language and that was stored in his session. 2. When he calls a new url, without the language prefix, the result page will use the selected language (stored in session), instead of the default language. Thanks, Everton ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
