Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <809863504.391071264057855353.JavaMail.jira@brutus.apache.org>
Date: Thu, 21 Jan 2010 07:10:55 +0000 (UTC)
From: =?utf-8?Q?Matthias_We=C3=9Fendorf_=28JIRA=29?= <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Updated: (TRINIDAD-1572) Potential Character Encoding
 problem in the Branch Trinidad-1.0.x
In-Reply-To: <1257015584.1252985637548.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/TRINIDAD-1572?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias We=C3=9Fendorf 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 bra=
nch

> 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 bran=
ch Trinidad-1.0.x. Hence, Trinidad-1.0.x remains vulnerable to the characte=
r encoding issue mentioned in Trinidad-1430. I will upload a patch to fix t=
his potential problem.

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