DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36738>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36738 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2005-09-27 00:11 ------- The short answer is that the behaviour you are seeing is as per the relevant specs and therefore this bug in invalid. The longer answer is: As per the section 8.4 of the JSTL 1.0 spec, use of <fmt:setBundle ...> results in a call to ServletResponse.setLocale() The servlet 2.3 spec states that a call to setContentType() or setLocale() can change the character encoding of the resposne. Therefore when running on TC4 the <fmt:setBundle ...> in localebad.jsp ultimately results in a call to setCharacterEncoding() which changes the encoding to Shift-JIS. The servlet 2.4 spec states that once the character encoding has been set by a call to setContentType() subsequent calls setLocale() must not change the character encoding. Therefore when running on TC5 the <fmt:setBundle ...> in localebad.jsp has no effect on the character encoding since it has aleady be set as a result of the intial page directive. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
