[
http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12408026 ]
Matija Mazi commented on RF-2914:
---------------------------------
I have the same (or similar) problem. I'm using JBoss Application Server 4.2.2 and
Seam 2.0.1.GA.
With RF 3.2.0 any international characters in forms are interpreted by the server
incorrectly. I get two strange characters instead of one interantional; it seems the
reqest is encoded in UTF-8 (as I want it to be) but the server interprets it as in some
8-bit encoding. The problem arises with RF 3.2.0, but not RF 3.1.4 (with no other changes
in application except RF version).
I don't get any nice error message as the one mentioned under in PWC4011 above, but
already before reading this I suspected that something like that could be the reason (some
part of the code reading request parameters before the request encoding is explicitly set
on the server).
I think this is a critical issue since it breaks normal functionality of any web
application that requires (or is supposed to accept) any text input other than English!
Error starting RichFaces enabled web application after switch to
3.2.0 release
------------------------------------------------------------------------------
Key: RF-2914
URL:
http://jira.jboss.com/jira/browse/RF-2914
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: jsf 1.2_08, glassfish 9.1
Reporter: Mareks Malnacs
Assigned To: Vladislav Baranov
Priority: Minor
Fix For: 3.2.2
Complex richfaces application works fine with 3.1.4 release. After update project
libraries to 3.2.0 glassfish displays following message in error log:
PWC4011: Unable to set request character encoding to UTF-8 from context /proc, because
request parameters have already been read, or ServletRequest.getReader() has already been
called
and firefox displays empty page.
If I switch back to 3.1.4 - application works fine.
Any changes in web.xml (or any other web-app configuration file) I am missed during
"upgrade" ?
Thanks,
Mareks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira