Well, at the least, it looks like it deserves a ticket. Pretty strange it only happens for one action though...
Don On 6/30/07, Ray Clough <[EMAIL PROTECTED]> wrote:
I have an application using S1, S2, and other component layers, all of which use Locale. At application startup, the InitializerFilter reads the user's previously stored Locale preference from a cookie. Then we are saving the Locale in the session. It works very well except for one glitch. When the Login page comes up (same Request cycle), we expected it to be Localized. The problem is that all pages EXCEPT the login page are Localized. We are saving it in the Session using the key 'I18nInterceptor.DEFAULT_SESSION_ATTRIBUTE', which has the value "WW_TRANS_I18N_LOCALE". Is this the correct key to be using? Any suggestions as to why the Login page might not be Localized? Stepping into the 'Text' tag code, the Locale is received from the Value Stack, not the ActionContext. Is some time or maybe one request cycle needed to propagate the newly set value in the Session to the Value Stack? If so, is that considered a bug? - Ray Clough -- View this message in context: http://www.nabble.com/-S2--Session-Key-for-Locale-tf4001507.html#a11365685 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
