[ https://issues.apache.org/jira/browse/TRINIDAD-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864852#action_12864852 ]
Vadim Dmitriev commented on TRINIDAD-1073: ------------------------------------------ ExternalContext mainly just delegates calls to the underlying context (PortletContext, ServletContext). ServletContext is provided by the container and will be different for Tomcat, WebSphere, WebLogic, etc. Real difference in client request processing lies there. I doubt it is possible to force application server to use custom servlet implementation, especially closed-source commercial appserver. > 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.