You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Michael Kurz (JIRA)" <de...@myfaces.apache.org> on 2007/11/15 16:26:43 UTC

[jira] Commented: (MYFACES-1768) MyFaces + Spring Webflow + UTF-8 Issue

    [ https://issues.apache.org/jira/browse/MYFACES-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542796 ] 

Michael Kurz commented on MYFACES-1768:
---------------------------------------

What I forgot: Thanks to Mr. Hsieh for pointing out the problem.

> MyFaces + Spring Webflow + UTF-8 Issue
> --------------------------------------
>
>                 Key: MYFACES-1768
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1768
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.2.1-SNAPSHOT
>            Reporter: Michael Kurz
>            Priority: Minor
>         Attachments: example-jira1768.zip
>
>
> I ran into some trouble with Myfaces 1.2.1-SNAPSHOT in combination with Spring Webflow and UTF-8. Even if all JSP pages have <%@ page contentType="text/html; charset=UTF-8" %> set, special characters like umlauts or arab characters are not displayed correctly in Tomcat 6. With Jetty it works.
> I did some debugging and found out that the charcter encoding of the ExternalContext is set in the restore view phase of JSF. BUT: Spring webflow adds a phase listener that reads request parameters before restore view. When the character encoding is not set correctly at this time (what seems to be the case with tomcat) strings get messed up. The problem can be easily solved with a servlet filter or a phase listener that sets the character encoding of the ExternalContext to UTF-8 before the Spring Webflow phase listener reads the request parameters.
> Nevertheless I would be interested if this is a bug and what piece of my chain is buggy. MyFaces, Webflow or Tomcat for obviously not setting the character encoding specified in the page. One thing seems to be clear: the character encoding must somehow be set before the Webflow phase listener is executed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.