tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Köberl (JIRA) <...@tapestry.apache.org>
Subject [jira] Updated: (TAPESTRY-1723) tapestry-upload does not use character encoding
Date Mon, 27 Aug 2007 12:19:30 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Christian Köberl updated TAPESTRY-1723:

    Attachment: fileupload_encoding_20070827.patch

This patch corrects the issue and also fixes the testcase (which failed because of the changes
in this patch).

> tapestry-upload does not use character encoding
> -----------------------------------------------
>                 Key: TAPESTRY-1723
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1723
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-upload
>    Affects Versions: 5.0.5
>            Reporter: Christian Köberl
>         Attachments: fileupload_encoding_20070827.patch
> tapestry-upload ignores the character encoding set in the request and falls back to default
character encoding. 
> The problem is that when extracting the parameter values the FileItem#getString() instead
of FileItem#getString(String encoding) is used. The same problem is described and solved in
JBoss Portal CMS:
> See also: http://jira.jboss.com/jira/browse/JBPORTAL-1550
> The getString method should be called with the encoding of the request: 
> item.getString(request.getCharacterEncoding());

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

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message