Return-Path: 
 <issues-return-19152-apmail-struts-issues-archive=struts.apache.org@struts.apache.org>
X-Original-To: apmail-struts-issues-archive@minotaur.apache.org
Delivered-To: apmail-struts-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 67BE9E505
	for <apmail-struts-issues-archive@minotaur.apache.org>;
 Tue,  4 Dec 2012 09:53:02 +0000 (UTC)
Received: (qmail 82453 invoked by uid 500); 4 Dec 2012 09:53:01 -0000
Delivered-To: apmail-struts-issues-archive@struts.apache.org
Received: (qmail 82312 invoked by uid 500); 4 Dec 2012 09:53:01 -0000
Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@struts.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@struts.apache.org>
List-Post: <mailto:issues@struts.apache.org>
List-Id: <issues.struts.apache.org>
Reply-To: dev@struts.apache.org
Delivered-To: mailing list issues@struts.apache.org
Received: (qmail 82209 invoked by uid 99); 4 Dec 2012 09:52:58 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 09:52:58 +0000
Date: Tue, 4 Dec 2012 09:52:58 +0000 (UTC)
From: =?utf-8?Q?Sebastian_G=C3=B6tz_=28JIRA=29?= <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <955182564.58183.1354614778945.JavaMail.jiratomcat@arcas>
In-Reply-To: <2049873345.16701.1353587459834.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (WW-3926) Inconsistent encoding behaviour in
 Struts 2.3.7 in JSPs, selects and submit buttons using i18n
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/WW-3926?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian G=C3=B6tz updated WW-3926:
-------------------------------

    Attachment: ww3926.zip

After some digging I found out, that the actual component causing the probl=
em is the tiles-plugin. When building the application without tile sit work=
s perfectly. Using tiles definitions for the same JSPs fails for none-ASCII=
 characters.

The attached project is actually an eclipse project. I am sorry it isn't a =
maven project.
               =20
> Inconsistent encoding behaviour in Struts 2.3.7 in JSPs, selects and subm=
it buttons using i18n
> -------------------------------------------------------------------------=
---------------------
>
>                 Key: WW-3926
>                 URL: https://issues.apache.org/jira/browse/WW-3926
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - Tiles
>    Affects Versions: 2.3.7
>         Environment: Tomcat 7, Linux, Java 1.6
>            Reporter: Markus Fischer
>             Fix For: 2.3.8
>
>         Attachments: ww3926.zip
>
>
> I experience some problems with umlauts after upgrading from Struts 2.3.4=
.1 to 2.3.7:
> Text with umlauts like '=C3=A4' from properties files get scrambled in th=
e JSPs, selects and submit buttons.
> file -i shows that properties file are encoded as iso-8859-1. which they =
should be, as far as I know. Recoding the properties files to UTF-8 actuall=
y resolves the problem for the JSPs. But within the selects and submit butt=
ons the problem persists.
> In addition text from a databases is also scrambled, but only in selects =
and not when using <s:property value=3D...
> This behaviour is new since version 2.3.7. I updated:
> - struts2-core
> - struts2-tiles-plugin
> - xwork-core=20
> Adding acceptcharset=3D"utf-8" to the forms does not help.
> I have in the JSPs <%@ page language=3D"java" contentType=3D"text/html; c=
harset=3DUTF-8" pageEncoding=3D"UTF-8"%> and <meta http-equiv=3D"Content-Ty=
pe" content=3D"text/html; charset=3DUTF-8">.
> Tomcat 7 is running with URIEncoding=3D"UTF-8"=20
> MySQL is used with pooled connections (c3p0) by connection with: jdbcUrl=
=3D"jdbc:mysql://127.0.0.1/mydatabase?useUnicode=3Dtrue&amp;characterEncodi=
ng=3DUTF-8...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira