It is true that once a page is loaded for a request, in a particular locale, that's fixed, even if you change the threads Locale using the ThreadLocale service.
On the other hand, if you inject the global Messages object (containing the contents of app.properties plus other things) that's actually a dynamic proxy that delegates to the correct instance matching the thread locale at the time you invoke methods. On Tue, Aug 23, 2011 at 1:05 AM, Stephan Windmüller <stephan.windmuel...@tu-dortmund.de> wrote: > Hello! > > Is it possible to change the language of injected messages during the page > rendering? > > Background: The exception report page shows the user a localized error. The > user has the option to forward a bug report to the administrator, but this > report should always be in English. > > I tried to change the ThreadLocale but it seems once the messages are > injected there is no way to change the language. > > Regards > Stephan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
