Bug 7596 - If the <fmt:message> doesn't properly set the javax.servlet.jsp.jstl.fmt.request.charset attribute when establishing a localization context.
Summary: If the <fmt:message> doesn't properly set the javax.servlet.jsp.jstl.fmt.requ...
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: All All
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2002-03-29 00:58 UTC by Ryan Lubke
Modified: 2004-11-16 19:05 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Lubke 2002-03-29 00:58:30 UTC
This is related to 7595.

  <fmt:message key="mkey" bundle="${application.tBundle}"/>

According to section 8.4, page 8-76:
  "After an action has called ServletResponse.setLocale(), it must
   determine the character encoding associated with the locale (by
   calling ServletResponse.getCharacterEncoding()) and store it in
   the 'javax.servlet.jsp.jstl.fmt.request.charset' session attribute."
Comment 1 Jan Luehe 2002-03-30 01:29:25 UTC
Yes, this is related to 7595.

Setting the response locale and storing the associated char encoding in the
'javax.servlet.jsp.jstl.fmt.request.charset' session attribute are implemented
by the same method

Now that this method gets called as a fix for 7595, it automatically also fixes
this (7596) bug.