Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 49274 invoked from network); 5 May 2010 14:51:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 May 2010 14:51:27 -0000 Received: (qmail 81695 invoked by uid 500); 5 May 2010 14:51:27 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 81640 invoked by uid 500); 5 May 2010 14:51:27 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 81633 invoked by uid 99); 5 May 2010 14:51:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 May 2010 14:51:27 +0000 X-ASF-Spam-Status: No, hits=-1546.3 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 May 2010 14:51:26 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o45Ep5lG027370 for ; Wed, 5 May 2010 14:51:05 GMT Message-ID: <11117795.21961273071065804.JavaMail.jira@thor> Date: Wed, 5 May 2010 10:51:05 -0400 (EDT) From: "Paul Mander (JIRA)" To: dev@myfaces.apache.org Subject: [jira] Issue Comment Edited: (TRINIDAD-1073) Character encoding problem with PPR on IBM WebSphere 6.0 In-Reply-To: <145623937.1210633015851.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TRINIDAD-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864301#action_12864301 ] Paul Mander edited comment on TRINIDAD-1073 at 5/5/10 10:50 AM: ---------------------------------------------------------------- The post http://old.nabble.com/-Trinidad--forced-UTF-8-in-PPR-responses--ts27545426.html#a27545426 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. The corruption appears to be on the request rather than the response - debugging the setter of my inputtext shows "?" for a ppr request, but fine for a full submit and updating the XmlHttpServletRequest to set encoding to iso-8859-1 has no impact. I have tested this with Trinidad 1.0.11 on WAS 6.1. on Trinidad 1.2.10 (myfaces 1.2.5) running on tomcat 6, this issue does not occur. I'll attempt to find out the differences in these environments. was (Author: pmander): The post http://old.nabble.com/-Trinidad--forced-UTF-8-in-PPR-responses--ts27545426.html#a27545426 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. The corruption appears to be on the request rather than the response - debugging the setter of my inputtext shows "?" for a ppr request, but fine for a full submit and updating the XmlHttpServletRequest to set encoding to iso-8859-1 has no impact. > 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.