Hello all! this is still an open thread for me. It's horrifying...
Any help highly appreciated! Regards, Bernhard -----Ursprüngliche Nachricht----- Von: Hirschmann, Bernhard Gesendet: Donnerstag, 13. Februar 2003 19:15 An: 'Struts Users Mailing List' Betreff: AW: bean:message problems with i18n James, thanks for your help! I tried it in different browser types and in different windows. So this appears also in different HTTPSessions. I can reload as much as I want, and I do not use any proxies for that. So I guess it is not a caching issue. I checked the <html:html> tag. The lang attribute has always the correct value, like set in the Action.setLocale() method. However, the wrong messages are always in the language, in which the <bean:message> tag has requested the message the very first time. The fallback mechanism just doesn't work anymore. Does the <bean:message> tag use some kind of caching using the resources? I also tried to switch back to struts 1.1b2, but with the same result. Bernhard -----Ursprüngliche Nachricht----- Von: James Childers [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 13. Februar 2003 18:57 An: Struts Users Mailing List Betreff: RE: bean:message problems with i18n Have you tried opening up a new browser and trying again? Sounds like it may be a caching issue. Also, check that your <html:html> tag is generating the correct "lang" attribute. Reload the page and view source, then check the HTML tag. -= J > -----Original Message----- > From: Hirschmann, Bernhard [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 13, 2003 11:41 AM > To: Struts User Mailing List (E-Mail) > Subject: bean:message problems with i18n > > We have big problems with the use of the i18n messages, used with the > bean:message tag. But the problems encounter only in a > special scenario: > > 1.) A German user loggs in -> a German locale is set using > Action.setLocale() > > -> exploring some JSPs, all messages are in German, that's good. > > 2.) The German user loggs out. > > 3.) A English user loggs in -> a English locale is set using > Action.setLocale() > > -> all messages already show in 1.) are still shown in > German. But messages > from other JSPs not visited in 1.) are shown correctly in English. > > > We use two ApplicationResources: > ApplicationResources.properties (the fallback version, in > English language) > ApplicationResources_de.properties (the German variant) > > > It seems to me, that the mechanism using the > ApplicationResources is the > reason, but I'm not sure... I debuged through the sources but > didn't find > the problem. > > Another strange thing is, that this has worked earlier, but > now something > must have happend while our further developing processes, so > that this 'bug' > is appearing. So I tried some older versions of this product > we delivered to > our customers, and suddenly in those versions is this bug > also present. > Maybe something on our application server has happend (WS > 4.0.4), but I have > no clue what this could be... In WSAD 4.0.2 it's the same > like in WS 4.0.4. > > Any hint is highly appretiated. (I'm working on this the > whole day now...) --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
