Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <482162537.1218539204212.JavaMail.jira@brutus>
Date: Tue, 12 Aug 2008 04:06:44 -0700 (PDT)
From: "Mark van den Boomen (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Commented: (TRINIDAD-1173) Character encoding problem when
 submitting with PPR and a filter getting parameters out the request
In-Reply-To: <1849454200.1218192104214.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-1173?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
2621771#action_12621771 ]=20

Mark van den Boomen commented on TRINIDAD-1173:
-----------------------------------------------

I changed the page as you suggested. The result is that the page submits th=
e value, but doesn't update the components with the triggers. With the debu=
gger I still see the wrong encoded string getting set in the bean. After a =
'manual refresh' the (malformed) value is also shown in the browser.

After removing the <html>-tag the PPR works fine, but the problem still occ=
ures.

> Character encoding problem when submitting with PPR and a filter getting =
parameters out the request
> -------------------------------------------------------------------------=
--------------------------
>
>                 Key: TRINIDAD-1173
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1173
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.2-core, 1.0.3-core, 1.0.4-core, 1.0.5-core, 1.0.=
6-core, 1.0.7-core,  1.0.8-core, 1.0.9-core
>         Environment: JSF RI / Myfaces 1.1.4
> Embedded OC4J of jDeveloper 10.1.3.1 / Oracle Application Server 10.1.3.1=
.0 / Apache Tomcat 6.0.18
> Firefox and Internet Explorer 7
>            Reporter: Mark van den Boomen
>         Attachments: AdfTrinidadTest.war, AdfTrinidadTest.zip
>
>
> If a form is submitted with PPR and the application uses a filter which r=
eads a parameter out of the request scope then somehow the character encodi=
ng screws up on other parameters. When the submitted value of a inputfield =
reaches the bean it's mallformed. This happends when the submitted value co=
ntains characters like '=C3=AB=C3=AC=C3=AF=C3=B2=C3=A4'. With a normal subm=
it this doesn't happen.
> Example:
> When 'Belgi=C3=AB' is submitted, the bean receives 'Belgi=C3=83=C2=AB'.
> The problem doesn't occur with Trinidad 1.0.1, so after spitting through =
the Subversion logs I noticed TRINIDAD-46 which was released with release 1=
.0.2 and replaces lots of the PPR. Maybe somewhere in the new implementatio=
n of PPR is the cause of the problem.
> As said the problem happens when a filter is getting a parameter from the=
 request (for example) like this:
>   String parameter =3D servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.

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