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 2010/01/21 08:10:55 UTC

[jira] Updated: (TRINIDAD-1572) Potential Character Encoding problem in the Branch Trinidad-1.0.x

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

Matthias Weßendorf updated TRINIDAD-1572:
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.12-core
           Status: Resolved  (was: Patch Available)

Thanks to Mamallan Uthaman for the patch; was already committed to 1012 branch

> Potential Character Encoding problem in the Branch Trinidad-1.0.x
> -----------------------------------------------------------------
>
>                 Key: TRINIDAD-1572
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1572
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions:  1.0.11-core
>         Environment: JSF1.1
>            Reporter: Mamallan Uthaman
>             Fix For: 1.0.12-core
>
>         Attachments: TRINIDAD-1572.patch
>
>
> Trinidad-1430 resolved a character encoding introduced by Trinidad-1272. But, unfortunately, the patch for the Trinidad-1430 didn't include the branch Trinidad-1.0.x. Hence, Trinidad-1.0.x remains vulnerable to the character encoding issue mentioned in Trinidad-1430. I will upload a patch to fix this potential problem.

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