https://issues.apache.org/bugzilla/show_bug.cgi?id=45957
Mihály Héder <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #5 from Mihály Héder <[EMAIL PROTECTED]> 2008-10-12 10:26:09 PST
---
I absolutely agree with André-John.
This particular issue has been a real showstopper for years and is the most
seriuos argument against Tomcat for non english-only applications. It makes
everything much harder than it should be:
1. you develop something, and you see that the accented characters are broken.
After some googling you find the request.setCharacterEncoding("UTF-8")
solution. You insert it into your code.
2. you troubleshoot by writing things out to stdout, and checking catalina.out
for results. You see that the encoding is still broken.
3. after painful hours you figure out that the request's encoding had been ok
since step 1, the problem is that _logging_ also has problems with encoding.
You lose some hair.
4. Things are ok with the requests but the UTF-8 responses are broken. Although
not mentioned in the wiki, you quickly find out that you should do
response.setCharacterEncoding("UTF-8");
That wasn't a big deal.
5. You want to use stuff (frameworks, etc..) developed by else and you don't
want to modigy the code. I'ts time to use the filter solution you have found in
the wiki. You modify your web.xml, insert the class (modified so that is sets
up response character encoding as well) into your jar. You had to do an hour or
so extra work but things are ok.
6. You move your stuff into production environment where there is a Sun Access
Manager or similar in front of your app. Things are broken again. After a lot
of research you figure out that the problem is with the filter chain, and your
only hope is to modify the main conf/web.xml, put your filter there. You
convince the sysadmin that it won't hurt else's webapps, another hours of work.
Agreed, there is a hack to solve every issue listed here but WHY must this be
so painful? I think utf8 should be the default, or configurable at least...
I see people getting stuck with this every now and then and they asking about
configuration options not code.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
