If it's anything like T4 you'll have to either do a redirect back to the same page or whatever mechanism is in place to "make a page active" somehow and have it do that to the same page.
All the i18n stuff probably happens in the very beginning while setting up the page/components/resources so it has to start over if you want to change locales. I'm sure you know more than I do about redirects/page activations in T5 though. On 8/14/07, Doug Hauge <[EMAIL PROTECTED]> wrote: > In several of our pages, the default locale we want to use for messages > depends on its activation context. We tried updating the locale using > 'ThreadLocale' from within the activate event handler, but it seems that > this is too late, for the page has already been loaded and all messages > in the template resolved using whatever locale was in effect at the time > of loading. Is there some way we can force the messages to be reloaded > after setting the thread locale in the activate event handler, or is > there some point before the page is loaded at which we can access the > page class and the activation context in order to set the locale? > > Thanks, > Doug > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
