Did you try using some logout JSP to invalidate that user's session, then try again without re-deploying the application? I believe LocalizationContext resides in the session scope for each user, so just shutting down the browser may not be sufficient, depending on your session/cookie settings. With an explicit logout page, you can end the session directly, shut down the browser, then try accessing the site again to see if on a new session the language setting gets picked up correctly.
Thomas Gideon Sr. Software Developer B2eMarkets 301.230.2236 Tel. 301.230.2248 Fax. [EMAIL PROTECTED] www.B2eMarkets.com > -----Original Message----- > From: Johann Uhrmann [mailto:johann.uhrmann@;xpecto.com] > Sent: Wednesday, October 30, 2002 8:36 AM > To: Tag Libraries Users List > Subject: JSTL: ResourceBundle lookup with fmt:message > > The unexpected behaviour: > > When the preferred languages in the browser are changed, the language > of the web site does not change. It needs a reload of the web > application to change the language according to the change in the > browser. -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
