Tapestry has built in support for including the language in the URL. If you set the locale on the PersistentLocale service, the first folder in the URL will be the language http://tapestry.apache.org/localization.html
There is also a ThreadLocale service which is ultimately used for message lookup. If you want your own custom logic then I suggest that you contribute a RequestFilter to the RequestHandler service. The RequestFilter will set the locale on ThreadLocale by inspecting the Request. It's probably best to contribute your filter "before:*" -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-call-locale-properties-file-based-on-urls-tp5719862p5719865.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
