You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Paul Mander <pa...@gmail.com> on 2010/05/05 12:25:21 UTC
Re: [jira] Commented: (TRINIDAD-1073) Character encoding problem
with PPR on IBM WebSphere 6.0
My Faces - Dev mailing list wrote:
>
>
> [
> https://issues.apache.org/jira/browse/TRINIDAD-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627707#action_12627707
> ]
>
> Matthias Weßendorf commented on TRINIDAD-1073:
> ----------------------------------------------
>
> any chance that there is an extra filter that queries the request params
> before the ExternalCtx implementation actually set the encoding ?
> What does your app do on Tomcat (I don't have WebSphere)
>
>> Character encoding problem with PPR on IBM WebSphere 6.0
>> --------------------------------------------------------
>>
>> Key: TRINIDAD-1073
>> URL: https://issues.apache.org/jira/browse/TRINIDAD-1073
>> Project: MyFaces Trinidad
>> Issue Type: Bug
>> Affects Versions: 1.0.7-core
>> Environment: MyFaces 1.1.5
>> IBM WebSphere 6.0
>> Windows XP SP2
>> Reporter: Vadim Dmitriev
>>
>> Input fields updated via PPR replace cyrillic characters with question
>> marks. There is no encoding problems if update is performed with ordinary
>> form submit.
>> Simple testcase:
>> create JSF page with tr:showDetailHeader containing tr:inputText. Type
>> some cyrillic characters in the input field. Close/open detailheader. As
>> a result cyrillic chars in the inputText will be replaced with question
>> marks.
>> There is no problem with encoding whatsoever if that showDetailHeader is
>> updated by ordinary update (navigation from/to that page, for example).
>> This problem is specific to WebSphere 6.0 (maybe 6.1 too, never had a
>> chance to check it). I tried the same testcase on OC4J 10.3.3.2 and
>> everything went fine.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
>
I'm seeing this issue on WebSphere 6.1 and Trinidad 1.0.11. Trinidad-1430
addressed part of this issue (in 1.0.12) but not totally. If I do a PPR on
an input text that contains cyrillic characters, they are replaced by "?".
--
View this message in context: http://old.nabble.com/-jira--Created%3A-%28TRINIDAD-1073%29-Character-encoding-problem-with-PPR-on-IBM-WebSphere-6.0-tp17197824p28459120.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (TRINIDAD-1073) Character encoding problem
with PPR on IBM WebSphere 6.0
Posted by Paul Mander <pa...@gmail.com>.
Paul Mander wrote:
>
> Just to follow up on this, there is a post
> http://old.nabble.com/-Trinidad--forced-UTF-8-in-PPR-responses--ts27545426.html#a27545426
> that questions the validity of code in XmlHttpServletResponse. I see that
> in my test case, the original encoding "ISO-8859-1" is replaced by utf-8
> but if I amend this code to use the original encoding, the issue still
> occurs.
>
and updating the XmlHttpServletRequest to set encoding to iso-8859-1 has no
impact. The corruption appears to be on the request rather than the response
- debugging the setter of the inputtext shows "?" for a ppr request, but
fine for a full submit
--
View this message in context: http://old.nabble.com/-jira--Created%3A-%28TRINIDAD-1073%29-Character-encoding-problem-with-PPR-on-IBM-WebSphere-6.0-tp17197824p28459799.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.
Re: [jira] Commented: (TRINIDAD-1073) Character encoding problem
with PPR on IBM WebSphere 6.0
Posted by Paul Mander <pa...@gmail.com>.
I'm seeing this issue on WebSphere 6.1 and Trinidad 1.0.11. Trinidad-1430
addressed part of this issue (in 1.0.12) but not totally. If I do a PPR on
an input text that contains cyrillic characters, they are replaced by "?".
Just to follow up on this, there is a post
http://old.nabble.com/-Trinidad--forced-UTF-8-in-PPR-responses--ts27545426.html#a27545426
that questions the validity of code in XmlHttpServletResponse. I see that in
my test case, the original encoding "ISO-8859-1" is replaced by utf-8 but if
I amend this code to use the original encoding, the issue still occurs.
--
View this message in context: http://old.nabble.com/-jira--Created%3A-%28TRINIDAD-1073%29-Character-encoding-problem-with-PPR-on-IBM-WebSphere-6.0-tp17197824p28459402.html
Sent from the My Faces - Dev mailing list archive at Nabble.com.