I believe "stray alpha particle" is the most likely answer. I'm on a US PC, with an English version of Windows XP. Everything on this machine screams English, but for some reason it's picking the application_fr.properties.
The forward for my logout action includes the attribute forward="true" to make sure that the request gets run through the filter, and I can see in the logs that it is. As far as I can tell Config is the correct way to set JSTL values and since I passed the same HttpSession instance into the Config.set that I used to set the Struts Global value, I can't see how it would have gotten the old session. I really don't want to have to try and debug into the black box that is Struts, but that's looking more and more likely (so much for saving time on this project by using a tried-and-true technology instead of rolling my own like I've always done in the past). (*Chris*) On 11/7/06, Christopher Schultz <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris, Chris Pratt wrote: > No the original problem statement was that the JSTL fmt tags were > picking up > the French text even though the locale was set to English Strange. Where is that French locale coming from? Default JDK locale? Locale of the web browser's headers? Stray alpha particle? > the Struts tags are working correctly. Okay, that makes sooo much more sense. > The only thing that I can think of is that the > Config class isn't working properly in this situation. With Struts I set > the Session Attribute directly, with JSTL, I used the Config.set() method. Is this happening in a request that is distinct from the one in which you did the invalidate? Or, might you be invalidating the request, and then doing a server-side forward to the code that re-sets this locale? I'm just wondering if it's possible that Config.set grabs the /old/ session identifier instead of the new one. Is Config.set the recommended way to set up data for the JSTL? As I said, I've never used it. Is there an alternate way? Say... poking a value directly into the session? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFURP89CaO5/Lv0PARAvGSAKCVIzPWw9HxIMEntWrl8y383UvOqQCgvfKz jki/ZLBndeuNBs+2d5hdnRg= =LaG0 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
