You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2010/02/12 20:56:28 UTC

[jira] Resolved: (MYFACES-2551) Set charset=iso-8859-1 using in facelets page makes current page not being rendered

     [ https://issues.apache.org/jira/browse/MYFACES-2551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-2551.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2

The encoding of the document takes precedence over "contentType" or "encoding" param from f:view, but if no xml declaration is used (like in mojarra examples), the value from contentType must be used as the response encoding (right now "encoding" or charset param set in "contentType" is just ignored). The original facelets code sets encoding always UTF-8.

It was asked to jsr-314-open list about that, but I think we can apply the proposed behavior without problem.

> Set charset=iso-8859-1 using <f:view> in facelets page makes current page not being rendered
> --------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2551
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2551
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-alpha, 2.0.0-beta
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.0-beta-2
>
>
> Pages starting like this:
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
>       xmlns:h="http://java.sun.com/jsf/html"
>       xmlns:f="http://java.sun.com/jsf/core"
>       xmlns:ui="http://java.sun.com/jsf/facelets">
> <f:view contentType="text/html; charset=iso-8859-1"/>
> are not rendered. If we remove charset=iso-8859-1, it works again.

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