You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org> on 2008/08/08 12:41:44 UTC
[jira] Created: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
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.9-core, 1.0.8-core, 1.0.7-core, 1.0.6-core, 1.0.5-core, 1.0.4-core, 1.0.3-core, 1.0.2-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
Priority: Blocker
Fix For: 1.0.1-core
If a form is submitted with PPR and the application uses a filter which reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
Example:
When 'België' is submitted, the bean receives 'België'.
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 implementation 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 = servletRequest.getParameter("test");
If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637041#action_12637041 ]
Mark van den Boomen commented on TRINIDAD-1173:
-----------------------------------------------
Hello Mathias and Matthias,
I traced the problem to the 'TrinidadFilterImpl'-class. Btw Adf11g also has the bug. After examining the source code of the 'TrinidadFilterImpl'-class I noticed that there is a bug in the filters 'doFilter()'-method which handles the somehow request incorrectly. Because I have trouble to recompile a working Trinidad-impl.jar using Maven, I created a filter to get arround this problem:
public class TrinidadPprBugFilter implements Filter {
private ServletContext _servletContext;
public void init(FilterConfig filterConfig) {
_servletContext = filterConfig.getServletContext();
}
public void doFilter(ServletRequest servletRequest,
ServletResponse servletResponse,
FilterChain filterChain) throws IOException,
ServletException {
ExternalContext externalContext = new ServletExternalContext(_servletContext, servletRequest, servletResponse);
if (CoreRenderKit.isAjaxRequest(externalContext))
servletRequest = XmlHttpConfigurator.getAjaxServletRequest(servletRequest);
filterChain.doFilter(servletRequest,servletResponse);
}
public void destroy() {
}
}
After placing this filter directly after the Trinidad or ADF 11g filter in web.xml the problems doesn't occur anymore.
So our problem is solved! And it works with no changes to the weppages.
It's maybe an idea to communicate this bug to the ADF11g developmentteam as the problem is 99% certain a bug in the filter.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621408#action_12621408 ]
Mark van den Boomen commented on TRINIDAD-1173:
-----------------------------------------------
I'm using FF2 and with FF3 the problem disappeared. So I tried setting all encodings of the JSP's and configuration files to the encodings 'windows-1252', 'ISO-8859-1' and 'UTF-8', but the problem still occures.
With UTF-8 the normal submit also fails to send with the correct encoding (FF2).
Have you looked at the attached AdfTrinidadTest.zip? In that sample application everything is set to 'windows-1252' but no luck.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Commented: (TRINIDAD-1173) Character encoding problem when submitting with PPR and a filter getting parameters out the request
Posted by Mathias Walter <ma...@gmx.net>.
Hi Mark,
> I changed the page as you suggested. The result is that the
> page submits the value, but doesn't update the components
> with the triggers. With the debugger I still see the wrong
> encoded string getting set in the bean. After a 'manual
I see the correct value.
What encoding does the 'Page Info' in FF show at your system?
--
Regards,
Mathias
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621771#action_12621771 ]
Mark van den Boomen commented on TRINIDAD-1173:
-----------------------------------------------
I changed the page as you suggested. The result is that the page submits the value, but doesn't update the components with the triggers. With the debugger 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 occures.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf resolved TRINIDAD-1173.
------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 1.0.1-core)
due some oddness in the servlet spec, when doing a query against the request parameter map, you can't specify the encoding afterwards.
So, put the filter behind the trinidad filter
> 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
> Priority: Blocker
>
> If a form is submitted with PPR and the application uses a filter which reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620905#action_12620905 ]
Matthias Weßendorf commented on TRINIDAD-1173:
----------------------------------------------
ok, I will re-check that.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Gary VanMatre (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary VanMatre updated TRINIDAD-1173:
------------------------------------
Status: Patch Available (was: Reopened)
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark van den Boomen reopened TRINIDAD-1173:
-------------------------------------------
> 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
> Priority: Blocker
> Attachments: AdfTrinidadTest.war, AdfTrinidadTest.zip
>
>
> If a form is submitted with PPR and the application uses a filter which reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mathias Walter (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777551#action_12777551 ]
Mathias Walter commented on TRINIDAD-1173:
------------------------------------------
I ran into this problem again with lightweight dialogs.
I analysed the POST request with FireBug and found that no character encoding is supplied at the request:
Response Header:
Server: Apache-Coyote/1.1
X-Powered-By: JSF/1.2
Content-Type: text/html
Content-Length: 58
Date: Fri, 13 Nov 2009 16:18:01 GMT
The content-type in all other PPR post response headers is "text/xml;charset=utf-8".
I also tried setting:
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
But that does not help either. Nor the tr:document tag helps.
The TrinidadPprBugFilter solved just the correct translation of the POST values, but did not changed the content-type. But it's a workaround for now.
> 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, RequestQueue.patch, test-webapp.zip
>
>
> If a form is submitted with PPR and the application uses a filter which reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mathias Walter (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620914#action_12620914 ]
Mathias Walter commented on TRINIDAD-1173:
------------------------------------------
Wich version of FireFox do you use?
I had the same problem with FF2 and IE*, but not with FF3. I tried different filters without luck.
Then I double checked all my xhtml files (templates as well). In a few of them I used a different encoding in the <?xml> tag.
I changed all to utf-8. Now the problem is gone.
Please check all your files (jsp, [x]html, etc.) and use the same encoding at all places.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mathias Walter (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621583#action_12621583 ]
Mathias Walter commented on TRINIDAD-1173:
------------------------------------------
If you use <%@ page contentType="text/html;charset=iso-8859-1"%>
and
<html>
<trh:head>
<title>tata</title>
</trh:head>
<trh:body>
instead of <tr:document>, it will work.
BTW: You don't have to change the encoding of configuration files, just the [x]html related files.
> 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 reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1173) Character encoding problem when
submitting with PPR and a filter getting parameters out the request
Posted by "Mark van den Boomen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620904#action_12620904 ]
Mark van den Boomen commented on TRINIDAD-1173:
-----------------------------------------------
I already tried that before opening this issue. In the sample application I uploaded, you can see that the filter is after the Trinidad filter in web.xml, but the problem still occures.
> 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
> Priority: Blocker
> Attachments: AdfTrinidadTest.war, AdfTrinidadTest.zip
>
>
> If a form is submitted with PPR and the application uses a filter which reads a parameter out of the request scope then somehow the character encoding screws up on other parameters. When the submitted value of a inputfield reaches the bean it's mallformed. This happends when the submitted value contains characters like 'ëìïòä'. With a normal submit this doesn't happen.
> Example:
> When 'België' is submitted, the bean receives 'België'.
> 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 implementation 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 = servletRequest.getParameter("test");
> If that line is removed from the filter Trinidad works normally.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.