[ http://issues.apache.org/jira/browse/TAPESTRY-757?page=all ]
Howard M. Lewis Ship resolved TAPESTRY-757:
-------------------------------------------
Resolution: Invalid
Well known issue that changes to the locale don't usually take effect until the
next request. This is discussed in Tapestry in Action, including how to work
around it.
> Locale cookie value is not set when the IEngine's locale is set
> ---------------------------------------------------------------
>
> Key: TAPESTRY-757
> URL: http://issues.apache.org/jira/browse/TAPESTRY-757
> Project: Tapestry
> Type: Bug
> Components: Framework
> Versions: 4.0, 4.1
> Reporter: Chris Norris
>
> The documentation for localization says this:
> In order to change the locale, you must obtain the IEngine and invoke
> setLocale() on it. This will change the value stored in the engine (which is
> used when loading new pages), and:
> * Update the hivemind.ThreadLocale service, allowing localized messages
> from services to be generated in the correct locale
> * Cause an HTTP Cookie to be added to the request so that future requests
> from the same client will be in the same locale
> From what I've seen of the code and in practice, this does not happen. If
> you want to just always use the user's browser's default locale, things work
> okay. But depending on IEngine's setLocale() method to change which
> .properties files are accessed doesn't work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
