I have set UTF-8 as the default everywhere - struts, tomcat, sitemesh.
I had a small breakthrough. It looks like it's a 2.1.6 specific issue. I
updated a development version to 2.1.8 and 2.2.1 and both worked fine. I
now have to find time to test the updated version for unintended
consequences.
Hi Zoran
can you confirm the encoding attribute at the top of your web.xml e.g.
?xml version=1.0 encoding=UTF-8?
in which case you *should* be able to map
U+00C6Æc3 86LATIN CAPITAL LETTER AE
http://www.utf8-chartable.de/
please confirm
Martin Gainty
That defines the encoding of the web.xml file itself...
On Oct 18, 2010 10:32 AM, Martin Gainty mgai...@hotmail.com wrote:
Hi Zoran
can you confirm the encoding attribute at the top of your web.xml e.g.
?xml version=1.0 encoding=UTF-8?
in which case you *should* be able to map
U+00C6Æc3
I did a quick look at the struts2.2.1 source code.
It looks like the method [HttpServletRequest.setCharacterEncoding]
is invoked by class [FilterDispatcher] and [StrutsPrepareFilter].
(You can use [Call Hierarchy] view to find out this information)
In your old configuration,
Sorry, type error:
In your old configuration, [StrutsPrepareFilter] is the last filter applied
to request
==
Should be:
In your old configuration, [FilterDispatcher] is the last filter
applied to request
2010/10/18 Li Ying liying.cn.2...@gmail.com:
I did a quick look at the struts2.2.1
I found the problem and it does not involve Struts 2.We changed
our SQL Server 2005 Text columns to varcharmax. For Java to properly
read the characters out of the DB we had to use rs.getCharacterStream.
Thank you for your help.
On Thu, Jul 3, 2008 at 5:01 PM, Laurie Harper [EMAIL
Richard Sayre wrote:
I have a form containing text areas. When I copy a bunch of character
data such as:
2öÂnJ1ÈÏúÄp8éÎdìåmðh4uæEÍÉieÔWán2ÅìbØÉÅÀ1JÎZÏôsC5LòÚAPúÜaÃÙPC5üÆCJWCOzùÙtÒQqùét
into the text are, it displays normally. When I save the data, the
database stores the characters properly,
Thanks a lot, that has sorted it out.
I'm a bit confused as to why changing the default from utf-8 works though...
Jonny Cavell wrote:
I am setting default_encoding=UTF-8 in freemarker.properties, and leaving
the struts encoding in default.properties untouched (i.e.
http://www.opensymphony.com/webwork/wikidocs/WebWork%20Freemarker%20Support.html
default-encoding needs to be set to ISO-8859-1 in freemarker.properties
more specifically:
default_encoding=ISO-8859-1 template_update_delay=5 locale=no_NO
strictement
interdit de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: riffla [EMAIL PROTECTED]
To: user@struts.apache.org
Sent: Friday, March 23, 2007 9:42 PM
Subject: Re: Character encoding...
Encoding set in:
JSP Page directive
Content
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
Encoding set in:
JSP Page directive
Content inside Html Meta tag
And there is also a charsetFilter class used (see below)
This last one is used for overriding /request/ encoding, right?
controller
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
Here's the content of the filter class:
[snip]
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain)
throws IOException, ServletException {
If you mean like System.out.println(request.getCharacterEncoding()) in top of
JSP, I guess I have, have to make a second check though, will return when
it's done. Really appreciate your aid, thanks
/Riffla
=
Christopher Schultz-2 wrote:
-BEGIN PGP SIGNED
And I guess that the form bean attributes is set prior to any code in the
form class, so that you can't set the characterEncoding in the form class
(at, for example, the beginning of initialize() method), or...?
Joe Germuska wrote:
I had problem with character encoding in my web application. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
And I guess that the form bean attributes is set prior to any code in the
form class, so that you can't set the characterEncoding in the form class
(at, for example, the beginning of initialize() method), or...?
Correct. You
Thanks for the reply
Actually, we do use a filter setting the encoding to UTF-8, though I'm not
sure if my problem is exactly the same as above.
Sending a request form a JSP using ISO-8859-1 with POST method (no problem
using GET method or UTF-8 on origin page) to either a Struts action or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
Sending a request form a JSP using ISO-8859-1 with POST method (no problem
using GET method or UTF-8 on origin page) to either a Struts action or
another JSP (with either UTF-8 or ISO-8859-1, tried both) replaces my å,ä
and
Of course, forgot to mention, mainly I mean as output on a JSP page (both
bean:write and %=...%, but also System.out.println() in different places,
always the same result...
/Riffla
Christopher Schultz-2 wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Riffla,
riffla wrote:
Of course, forgot to mention, mainly I mean as output on a JSP page (both
bean:write and %=...%, but also System.out.println() in different places,
always the same result...
The method of output is not relevant. Only the
Encoding set in:
JSP Page directive
Content inside Html Meta tag
And there is also a charsetFilter class used (see below)
Struts-config.xml contains:
===
controller contentType=text/html;charset=UTF-8
processorClass=org.apache.struts.tiles.TilesRequestProcessor/
===
web.xml contains:
===
qu'il est strictement interdit
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: riffla [EMAIL PROTECTED]
To: user@struts.apache.org
Sent: Friday, March 23, 2007 9:42 PM
Subject: Re: Character encoding...
Encoding set in:
JSP Page directive
Content
I had problem with character encoding in my web application. I was trying to
display Polish characters using UTF-8 but data from forms was not getting in
proper format to the business layer. I managed to solve this by setting
filter which does request.setCharacterEncoding(encoding); But the
On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
Now, I guess I'll just have to try using the character encoding filter
Guillaume recommended.
Ack! I'm about to pull my hair out over these encoding issues. I added
the SetCharacterEncodingFilter from the Tomcat 5 distribution to my web
J.Patterson Waltz III lists 'at' cerenit.com writes:
On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
Now, I guess I'll just have to try using the character encoding
filter Guillaume recommended.
Ack! I'm about to pull my hair out over these encoding issues. I added
the
On 6 janv. 05, at 17:17, Guillaume Cottenceau wrote:
J.Patterson Waltz III lists 'at' cerenit.com writes:
On 6 janv. 05, at 15:52, J.Patterson Waltz III wrote:
Now, I guess I'll just have to try using the character encoding
filter Guillaume recommended.
Ack! I'm about to pull my hair out over
J.Patterson Waltz III lists 'at' cerenit.com writes:
Notice in the third line of the form data:
personTO.comments=%C3%A9t%C3%A9
That's 'été' URLencoded as UTF-8.
So I'm still stumped. :-(
But that's exactly what you want. The SetCharacterEncodingFilter
will set the character encoding of
On 6 janv. 05, at 17:44, Guillaume Cottenceau wrote:
J.Patterson Waltz III lists 'at' cerenit.com writes:
Notice in the third line of the form data:
personTO.comments=%C3%A9t%C3%A9
That's 'été' URLencoded as UTF-8.
So I'm still stumped. :-(
But that's exactly what you want. The
J.Patterson Waltz III lists 'at' cerenit.com writes:
On 6 janv. 05, at 17:44, Guillaume Cottenceau wrote:
J.Patterson Waltz III lists 'at' cerenit.com writes:
Notice in the third line of the form data:
personTO.comments=%C3%A9t%C3%A9
That's 'été' URLencoded as UTF-8.
So I'm still
On 6 janv. 05, at 18:13, Guillaume Cottenceau wrote:
I also have another filter, the ResponseOverrideFilter used by
displaytag, which appears before the SetCharacterEncodingFilter in my
web.xml. I wonder if it could be interfering with the
SetCharacterEncodingFilter?
Yes, if it reads the request
J. Patterson Waltz III pattersonw 'at' hotmail.com writes:
P.S. - I know how to view the headers of replies sent from the server to the
browser, but am not sure how to get at those sent from the browser to the
server, to make sure that they are indeed UTF-8. Any suggestions?
I usually
in article [EMAIL PROTECTED], Josh Cronemeyer at [EMAIL PROTECTED] wrote
on 4/01/05 18:02:
J. Patterson Waltz III wrote:
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
J. Patterson Waltz III pattersonw 'at' hotmail.com writes:
Hello,
I recently upgraded a J2EE/Struts web application I'm working on to the
1.2.4 version of Struts, and ever since I made this change, I've been
encountering a problem with the encoding of non-ascii character data
submitted in
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=16191
I will try that out and see if it improves my results.
I remain perplexed at what changes between versions 1.1 and
J. Patterson Waltz III wrote:
Merci Guillaume,
I had actually seen the references to the Filter solution in the comments of
Struts bug 16191 in Bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=16191
I will try that out and see if it improves my results.
I remain perplexed at what
I'd like to hear how others have solved this problem. I can see
that one solution is to replace the RequestProcessor and hardcode the
setEncoding on the Request to UTF-8, or subclass the whole
ActionServlet. Are there any cleaner solutions? I can't believe I'm the
only one to
Carl-Eric,
Yes, I tried the charset on the form but found it didn't do any good.
But what do you force the Encoding to in your Filter? How can you
know with any certitude how the browser encoded the data values before
sending it to you?? It probably works well if the browser is
PROTECTED]
Sent: Wednesday, July 21, 2004 9:39 PM
To: Struts Users Mailing List
Subject: Re: character encoding
Carl-Eric,
Yes, I tried the charset on the form but found it didn't do any good.
But what do you force the Encoding to in your Filter? How can you
know with any
I have added an acceptCharset attribute to the FormTag.
html:form action=abc.do acceptCharset=UTF-8
which will generate something as
form action=abc.do method=post accept-charset=UTF-8
Should be available in the next nightly build - 22/07/2004
Niall
- Original Message -
From:
Here is a prebuilt filter that will do just what you are looking for ..
http://www.anassina.com/struts/i18n/i18n.html
Nathan
On Apr 20, 2004, at 6:00 AM, brelagad the ent wrote:
I cannot pass Turkish characters to the action servlet
from a form. I read that I should use filters. I am
wondering,
39 matches
Mail list logo
