You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mamallan Uthaman (JIRA)" <de...@myfaces.apache.org> on 2009/03/19 19:46:50 UTC
[jira] Updated: (TRINIDAD-1430) Character encoding problem with
Majorra introduced by issue TRINIDAD-1272
[ https://issues.apache.org/jira/browse/TRINIDAD-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamallan Uthaman updated TRINIDAD-1430:
---------------------------------------
Status: Patch Available (was: Open)
> Character encoding problem with Majorra introduced by issue TRINIDAD-1272
> -------------------------------------------------------------------------
>
> Key: TRINIDAD-1430
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1430
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.11-core
> Environment: JSF 1.2 RI (Majorra)
> Facelets 1.1.14
> Glassfish 9.1
> Reporter: Luka Surija
>
> TRINIDAD-1272 - Support for WAP2.0 Browser without JavaScript (svn revision 713294) introduced a character encoding problem with non-us characters with JSF RI (Majorra), Glassfish 9.1 and Facelets 1.1.14.
> The problem is not in displaying this characters, but in submitting. For example "šđžćč" is correctly displayed in tr:inputText, but after submitting the same value, it is displayed as "Å¡Ä'Å¾Ä‡Ä ". This problem is not only with croatian characters, but also with German umlauts and probably other non us characters.
> This error is related with error in server log:
> "PWC4011: Unable to set request character encoding to UTF-8 from context /, because request parameters have already been read, or ServletRequest.getReader() has already been called"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.