You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2009/03/18 14:19:50 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=12683015#action_12683015 ] 

Matthias Weßendorf commented on TRINIDAD-1430:
----------------------------------------------

in here:
 ExternalContext externalContext = new ServletExternalContext(_servletContext, request, response);  

we set the encoding (inside of the ServetExternalContext(...)), so the fix for 1272 should be done after that,
or we need to create the ServetExternalContext earlier...


> 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.